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's master branch has broken nix-build exit codes #4813
Comments
This appears to be broken when talking to the daemon, and not broken when using nix-build as root. |
It seems to be due to c43e882f54#diff-9338f330e24f13e71e33fcd53698bb563f916fb823331f0484c1a1674974e896R928-R934 : With a new-enough daemon, the communication of the exceptions from the daemon to the client now uses an overload of operator << and readError, but it looks like these don’t transmit the |
I wonder if it would be easier to keep these working if the client always transmitted data to the daemon and back using data objects, serialized or not like protobufs or something -- regardless of if it is actually talking to the daemon or not. |
That could greatly help, yes. I think it might have some performance implications on some-cases because bypassing the daemon can prevent from having to send big things like Nar archives down the wire − IIRC the hydra runners run in daemonless mode just for that. But that could be mitigated by special-casing some operations (the same way Nix occasionnally directly reads stuff from the store even when using the daemon). Now of course that’s quite a big refactoring to make, so… 🙃 |
I marked this as stale due to inactivity. → More info |
Describe the bug
nix-build should exit based on how the build failed. For example, from the docs:
However, this is currently broken:
Steps To Reproduce
Expected behavior
Nix should exit with the documented exit codes.
nix-env --version
outputnix-env (Nix) 2.4pre20210514_de9e43c
Additional context
NixOS unstable
The text was updated successfully, but these errors were encountered: