Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wakatime: Explicit checkPhase #32935

Closed
wants to merge 1 commit into from
Closed

Conversation

markus1189
Copy link
Contributor

The actual tests write to the filesystem and lead to errors, so I replaced them with a different sanity check for the version

Related #32244

@jtojnar
Copy link
Contributor

jtojnar commented Dec 21, 2017

The write errors can be fixed by adding

  preCheck = ''
    export HOME=$(mktemp -d)
  '';

@markus1189
Copy link
Contributor Author

Ah nice 😎

But unfortunately the tests run and fail with assertion errors :(

@@ -1,7 +1,8 @@
{ stdenv, buildPythonApplication, fetchFromGitHub }:

buildPythonApplication rec {
name = "wakatime-${version}";
baseName = "wakatime";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pname

@@ -1,7 +1,8 @@
{ stdenv, buildPythonApplication, fetchFromGitHub }:

buildPythonApplication rec {
name = "wakatime-${version}";
baseName = "wakatime";
name = "${baseName}-${version}";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

name can be dropped

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it default to ${pname}-${version}?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In buildPython*, yes.

The actual tests write to the filesystem and lead to errors

Related NixOS#32244
@FRidh
Copy link
Member

FRidh commented Dec 23, 2017

But unfortunately the tests run and fail with assertion errors :(

And they're not fixable?

@markus1189
Copy link
Contributor Author

I don't know, I did not test :D

@jtojnar
Copy link
Contributor

jtojnar commented Jan 16, 2018

Tests were disabled in #33917

@jtojnar jtojnar closed this Jan 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants