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

nix-thunk installation error on WSL: clock resolution test failures #23

Closed
AlexKnauth opened this issue Jan 20, 2022 · 3 comments
Closed

Comments

@AlexKnauth
Copy link

AlexKnauth commented Jan 20, 2022

Attempting to install nix-thunk on my Windows machine with WSL failed with:

2 out of 859 tests failed (0.89s)
Test suite main: FAIL
Test suite logged to: dist/test/time-compat-1.9.5-main.log
Test suite instances: RUNNING...
Test suite instances: PASS
Test suite logged to: dist/test/time-compat-1.9.5-instances.log
1 of 2 test suites (1 of 2 test cases) passed.
error: builder for '/nix/store/f9wmpfxabiv5fm9y6jsw8iq6hlq5z865-time-compat-1.9.5.drv' failed with exit code 1
error: 1 dependencies of derivation '/nix/store/kmp88r7jz7wxmdyv8gh5yd77c33m1rw1-aeson-1.5.6.0.drv' failed to build
error: 1 dependencies of derivation '/nix/store/pghmx6vrbjr2q00a4zak9r08nfz8in1i-quickcheck-instances-0.3.25.2.drv' failed to build
error: 1 dependencies of derivation '/nix/store/7czl3495cdbvzlb618qx8a72ql39d5s3-nix-thunk-0.3.0.0.drv' failed to build

Two of the test failures before this were:

    resolution
      getCurrentTime:                                                             FAIL (0.14s)
        test/main/Test/Clock/Resolution.hs:57:
        resolution
        expected: 0.000000001s
         but got: 0.0000001s
      taiClock:                                                                   FAIL (0.15s)
        test/main/Test/Clock/Resolution.hs:57:
        resolution
        expected: 0.000000001s
         but got: 0.0000001s
@AlexKnauth AlexKnauth changed the title nix-thunk installation test failures on WSL nix-thunk installation error on WSL: clock resolution test failures Jan 20, 2022
@kmicklas
Copy link
Collaborator

The failure is from the time-compat package, you should probably report the issue there instead.

@Yasuke
Copy link

Yasuke commented Jan 20, 2022

Yes you can get around this buy having a cache or something that you can pull from instead of compiling from scratch. The time resolution just isn't high enough in WSL (maybe in the WSL2 on windows 11 with gpu support?)

@AlexKnauth
Copy link
Author

How would I install nix-thunk using a cache instead of compiling on WSL?

I'm currently using WSL2 on Windows 10.

I also opened an issue on time-compat here: haskellari/time-compat#31

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants