nix no longer tells me why I can't build remotely #1572
Comments
|
As an aside, with the closer integration between nix and the "build hook", it'd be nice if the debug messages were more helpful than just decline :) (ssh failed, wrong arch, busy, trusted users not setup right, missing feature X) |
|
Added some debug logs in #3425 |
|
I would definitely appreciate more logs about this topic!
But this still is not enough for me. Why doesn it not work? I'm building with and have in my so perhaps it's that it doesn't want to build on I think the Edit for my memory: Workaround from the commandline: nix-store -r --builders 'ssh://static-haskell-nix-ci x86_64-linux - - - big-parallel,kvm' --option builders-use-substitutes true --max-jobs 0 |
|
cc @arianvp since he got this error yesterday. Seems to be a problem with feature flags, architecture mismatch or lack of trusted-users permission. |
|
This indeed cost me at least 2 days of braintwisting. I was missing a logging why something is |
domenkozar
added
error-messages
|
I moved the debug logs now to this seperate PR: #3586 |
Aha! This weekend I hit an issue where my build refused to compile LLVM on my enormous remote build machine, and since I couldn't figure out why I resorted to just waiting for it to compile locally on my laptop. If it's any consolation, your comment saved me a good bit of debugging :) |
|
It looks like this particular error has a nice proposal for improvement in @bburdette's https://github.com/bburdette/nix-error-proposal/blob/master/proposal.md#error-example Looking forward to the day when this scenario produces this instead! |
|
Today, I've also stumbled over this issue. There is really no good way to debug this. :( I've already donated to https://opencollective.com/nix-errors-enhancement :) |
|
The C++ "none of the overloads of the function matches your call" errors I've been seeing a lot lately (:D :D :D) are a user interface. We might learn from them in e.g. sorting the builders by "distance" to the request, and perhaps only showing n closest matches. |
|
PR #3897 helps with this. |
Also further improve the final error message, giving a practical example of how to set machine features because that's what most people need to succeed in building large packages remotely.
|
I made a follow-up PR to add more details in #3927. |
Also further improve the final error message, giving a practical example of how to set machine features because that's what most people need to succeed in building large packages remotely.
Also further improve the final error message, giving a practical example of how to set machine features because that's what most people need to succeed in building large packages remotely.
Also further improve the final error message, giving a practical example of how to set machine features because that's what most people need to succeed in building large packages remotely.
|
I marked this as stale due to inactivity. → More info |
|
I hit this attempting to remote build a system configuration. Helping with the search-ability a bit: results in The fix is to add big-parallel explicitly as mentioned above: |
|
I marked this as stale due to inactivity. → More info |
|
Still an issue. Took me half an hour to figure out what was wrong here, with the relevant line buried in thousands of lines of logs. I should not have to crank up the verbosity so much to get that error report. The culprit turned out to be: IMHO this particular case should not trigger a log entry that only shows up on high verbosity levels, but a hard error: I was clearly using this tool wrong. |
Also further improve the final error message, giving a practical example of how to set machine features because that's what most people need to succeed in building large packages remotely.
roberth
added
the
remote build
Derivation in question is a
fetchgitderivation. In nix 1.11, when a remote builder refused to build a derivation, or nix didn't bother asking the remote builder, there would be a debug message along the lines ofhook reply is "decline". No such message is printed anymore, making it a lot harder to figure out what's going wrong:The text was updated successfully, but these errors were encountered: