-
Notifications
You must be signed in to change notification settings - Fork 6
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
Strange test failure on remote builder #20
Comments
Been told that this happens for other as well for tests executed with >= 12 jobs, but not as reliable as in our case. |
sternenseemann
added a commit
to NixOS/nixpkgs
that referenced
this issue
May 22, 2021
hspec is invoked with -j1 in the hopes that this migitates the issue of the current failures on Hydra: vmchale/libarchive#20
Unfortunately I've gotten that as well (sporadically), not sure why but I'll have a look. Flaky test suite on my part I think. |
Haven't been able to reproduce with GHC 9.0.1 (x86) |
Only tested GHC 8.10.4. I guess I’ll try again when we have switched to that as the default version.
… On 2. Jun 2021, at 20:43, Vanessa McHale ***@***.***> wrote:
Haven't been able to reproduce with GHC 9.0.1 (x86)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I believe this should be fixed in 82d7f6a#diff-0a195188bdcf4bdc24fe5ec180dbcf24e4ca482168ffc057ba71c55eceae0b99 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I haven't been able to figure out this test failure occurring on a builder of our nixpkgs CI infrastructure. It happens consistently on different builders, but only on
x86_64-linux
ones. I can't reproduce it locally at all.My best guess it has something to do with parallelization of the test in question maybe. The builder passes
-j16
everywhere, so I guess that is also whathspec
detects. Not sure what of the test could not be threadsafe so far, had a look attemporary
and it all seemed reasonable…The text was updated successfully, but these errors were encountered: