-
Notifications
You must be signed in to change notification settings - Fork 104
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
Test suite fails on i686 (32-bit) #431
Comments
10 tasks
nh2
added a commit
to nh2/nixpkgs
that referenced
this issue
Mar 28, 2020
The tests have x86_64 results hardcoded, see hspec/hspec#431. (cherry picked from commit 59e77d45b234162e2a6b804fe9c1462e6089afe8)
10 tasks
nh2
added a commit
to nh2/nixpkgs
that referenced
this issue
Mar 28, 2020
The tests have x86_64 results hardcoded, see hspec/hspec#431.
@nh2 if rewriting the tests by e.g. using |
peti
pushed a commit
to NixOS/nixpkgs
that referenced
this issue
Apr 3, 2020
The tests have x86_64 results hardcoded, see hspec/hspec#431.
stigok
pushed a commit
to stigok/nixpkgs
that referenced
this issue
Jun 12, 2020
The tests have x86_64 results hardcoded, see hspec/hspec#431. (cherry picked from commit 59e77d45b234162e2a6b804fe9c1462e6089afe8)
Can't reproduce on a Vagrant box with I'm going to close this, but still happy to accept any patches. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://nix-cache.s3.amazonaws.com/log/vhbn2z10qrl9by4z2rrjc9gj98ixkv93-hspec-core-2.7.1.drv (from here) shows failures that seem to happen only on 32-bit Linux.
Perhaps this is related to
Int
being used in the test itself, orStdGen
?Could the tests be written so that they pass on both 32- and 64-bit?
The text was updated successfully, but these errors were encountered: