nix-build: requires non-existent output 'out' from input derivation #6572
Comments
same here with i have to call
this is after nix garbage collect = empty store. no problem with populated store build log nix-build.qt6.qtwebengine.nix-bug-6572.log input: relevant logs
the "removing invalid path" looks suspicious |
|
My guess would be nix starting the next build too early before the outputs of the previous build is properly registered. |
|
aka in something simple as { pkgs }:
with pkgs;
let
x = fetchFromGitHub {
# ...
};
in
stdenv.mkDerivation {
buildInputs = [ x ];
# ...
}this time, restarting the build does not help i have to manually eval the first derivation to fix this nix-build -E 'with import <nixpkgs> {}; with pkgs; fetchFromGitHub {
owner = "milahu";
repo = "gnumake-tokenpool";
rev = "5dabefe12144bb91b3bf9b8ec67004282e6f0f18";
sha256 = "6CfKYQgYSzR/8Nule7gWkwn0W9crqlWcgPIr39LUYsk=";
}'this works as expected
aka
... where source is a |
|
This issue is wreaking havoc on our CI. Fortunately it turns out that it is at least perfectly reproducible there, so I was able to bisect it using the Hydra binary tarballs down to the merge of #6227 /cc @edolstra. Which at least seems plausible as that PR directly changed the conditional leading to the error: https://github.com/NixOS/nix/pull/6227/files#diff-5784d1ad7c22601c75b86872534049bea5173377de5d61b7446452beabc16d3fL491-R534 |
|
most nixpkgs staging PRs have this issue in |
workaround for NixOS/nix#6572
workaround for NixOS/nix#6572
|
I am suffering from this too and downgraded to nix 2.7. |
|
Hopefully this is somewhat helpful, but I'm experiencing this (1) seemingly more lately, (2) almost every time I have a large cross-compile rebuild. Not sure if it's the cross-compile part, the large build part, or if it's a misnomer. I know that when I cross rebuild my risc-v config, I basically need to instead run edit: my current |
|
Edit: I guess |
EDIT: Disregard, I can trigger this from a cold boot. |
|
We hit this in CI where looping forever is not an option.
…On Sun, Oct 2, 2022, 10:33 PM endgame ***@***.***> wrote:
Edit: I guess while true; do nixos-install; done is a solution for now.
Not completely. I sometimes like to stress-test my computer and nixpkgs by
running nixos-rebuild --no-net, and after looping for a while I was
unable to build anything really because any build would fail with "too many
open files". So I suspect when this bug is triggered and the build is
aborted, Nix is not closing open files properly.
—
Reply to this email directly, view it on GitHub
<#6572 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABBACRF7FXIDP5MLUQOU4ODWBJAX3ANCNFSM5W6EUWFA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/content-addressed-nix-call-for-testers/12881/206 |
|
My rough guess is that this is one of the many bugs that arose with the implementation of impure derivations #6227 |
|
@Ericson2314 : You added this portion back in 2020: 2de2012 The 6227 PR removed that fix. But the equivalent fix from that commit near (https://github.com/NixOS/nix/pull/6227/files#diff-5784d1ad7c22601c75b86872534049bea5173377de5d61b7446452beabc16d3fR412) was not removed. So it seams either both are need or neither. But i don't see a logic error in the translation between the two. @Kha you mentioned you had a reproducer? |
|
I am also able to reproduce this on our CI system. I have a build that fails with this every time. It always seems to be the same derivation failing with this error as well. Will have a look at the details, to see which one. |
|
How is this bug still open after 6 months. I’m gonna pin nix to 2.7 or 2.6 until it is closed. |
|
@Profpatsch because people's understanding has been slowly evolving over those six months. I mean, it was only eight days ago that @Kha posted a very good theory about what's really going on. Also note that older Nix is technically affected, but it's much harder to trigger. |
|
I get the feeling it was not seen as very high priority. |
|
I revived nix 2.6 in nixpkgs NixOS/nixpkgs#200357 |
|
It seems that a dependency between the multi-outputs is required: #7283 |
The critical regression bug in NixOS/nix#6572 does not appear (at least as often) in nix 2.6 according to the discussion there, so we need to allow people to pin this older version. Partial revert of NixOS@b2eea05
The critical regression bug in NixOS/nix#6572 does not appear (at least as often) in nix 2.6 according to the discussion there, so we need to allow people to pin this older version. Partial revert of b2eea05
The critical regression bug in NixOS/nix#6572 does not appear (at least as often) in nix 2.6 according to the discussion there, so we need to allow people to pin this older version. Partial revert of NixOS@b2eea05
(cherry picked from commit c279ddb)
(cherry picked from commit c279ddb)
(cherry picked from commit c279ddb)
|
🎉 |
[Backport 2.11-maintenance] Fix #6572 `requires non-existent output`
The critical regression bug in NixOS/nix#6572 does not appear (at least as often) in nix 2.6 according to the discussion there, so we need to allow people to pin this older version. Partial revert of NixOS@b2eea05
Describe the bug
Packages build fails very often:
I have to restart the build process manually each time.
The problem happens on nix versions 2.8.1 and 2.9.0pre20220512_d354fc3
On version 2.8.0 the problem rarely occurred
The text was updated successfully, but these errors were encountered: