-
-
Notifications
You must be signed in to change notification settings - Fork 310
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
hydra-eval-jobs masks error messages from Nix (again) #822
Comments
So yeah, my eval was wrong, but hiding the message is still problematic. And hopefully is the same root cause anyway for hiding the message in the problem at hand. |
We're facing an issue with masking of an error again NixOS/nixpkgs#108304. |
@edolstra can we have a review of the C++ code from someone that knows about the implementation, so it can then be fixed and merged? |
#1025 to fix a different class of failure |
Looking at the following:
I had an inkling of a doubt that it was a similar issue to what was found previously. Where the error message the evaluator gives us is not related to the error that matters. (#728)
The final output of the evaluator, on my end, reduced:
That doesn't sound helpful. I tried using
strace
like the last time it happened. A big 20GiB file, but a quicktail -n 9999 trace.strace > reduced.strace
and we can look at it.tail -n 130 reduced.strace
More lines in this gist (6.7MiB!).
The error is
preallocating file of 20528731521 bytes: No space left on device
. (This is 20.53GB.)So it's failing around here, in Nix, but Hydra totally masks that from the evaluator output.The issue to fix here, is not the issue that Nixpkgs was having. The issue to fix is to ensure Hydra properly transmits all the information it gets to the end-users who are debugging issues with eval.
Sorry, I don't have much of a reproducer, except to run the evaluator with the problematic commit:
Reducing the test case (sorry) is left as an exercise to the reader (for now).
This was run using 405c52b. The currently deployed hydra.
cc: NixOS/nixpkgs#93457The text was updated successfully, but these errors were encountered: