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
Remote builds unconditionally triggering use-case-hack #2009
Labels
Comments
edolstra
added a commit
to edolstra/nix
that referenced
this issue
Mar 27, 2018
edolstra
added a commit
to edolstra/nix
that referenced
this issue
Mar 27, 2018
Allow global config settings to be defined in multiple Config classes. For example, this means that libutil can have settings and evaluator settings can be moved out of libstore. The Config classes are registered in a new GlobalConfig class to which config files etc. are applied. Relevant to NixOS#2009 in that it removes the need for ad hoc handling of useCaseHack, which was the underlying cause of that issue.
coreyoconnor
pushed a commit
to coreyoconnor/nix
that referenced
this issue
Mar 28, 2018
coreyoconnor
added a commit
to coreyoconnor/nix
that referenced
this issue
Mar 28, 2018
The patch at ac19837 contains a change worth considering: always remove the "nix I'm using this to recover from the corrupted nix store by, essentially, transferring the NARs to the same computer. (A weird effect of having nix-serve serve the store being repaired!) |
This was referenced Apr 10, 2018
edolstra
added a commit
that referenced
this issue
May 30, 2018
Allow global config settings to be defined in multiple Config classes. For example, this means that libutil can have settings and evaluator settings can be moved out of libstore. The Config classes are registered in a new GlobalConfig class to which config files etc. are applied. Relevant to #2009 in that it removes the need for ad hoc handling of useCaseHack, which was the underlying cause of that issue.
Anton-Latukha
pushed a commit
to Anton-Latukha/nix
that referenced
this issue
Jul 12, 2018
Allow global config settings to be defined in multiple Config classes. For example, this means that libutil can have settings and evaluator settings can be moved out of libstore. The Config classes are registered in a new GlobalConfig class to which config files etc. are applied. Relevant to NixOS#2009 in that it removes the need for ad hoc handling of useCaseHack, which was the underlying cause of that issue.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On my ARM builder's master machine (an old x86_64 NixOS laptop) some paths have the case hack applied without any involvement of MacOS machines:
On the slave (an ARMv7 NixOS board) the path is fine, i.e. the case hack suffixes don't exist.
If I gc the path on master and realize the derivation again (i.e.
nix-store -r /nix/store/j06agj9f3s3v44xyh27048wrmh0w09iw-linux-headers-4.15.drv
) the problem is reproduced, i.e. the case hack suffixes are still there. If I copy-closure the path from the slave, the path is fine on the master as well.Both have Nix 2.0.
I suppose the real problem is:
and somewhere in the remote build path the above gets triggered even if the value is set to
false
, as I'm guessing from thisuse-case-hack\0\0\0\5\0\0\0\0\0\0\0false\0\
which is written to the/nix/store/lg0s7z1bvj2chimz3a4qax3y8ssw45m3-nix-2.0/libexec/nix/build-remote
process via a pipe:The text was updated successfully, but these errors were encountered: