-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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: revert default to 2.18 for now #343032
Conversation
Running nixpkgs-review to see if there's anything else that needs reverting. |
Seems like the |
I am not so sure about that. It could be any nixos configuration causing this really. |
Yeah, maybe if someone finds an expression that reproduces this consistently, we can add it to the upstream test suite, but this feels way too flaky. |
Please include reasons for reverts in commit messages. |
606658f
to
24d85d5
Compare
Updated commit messages, added nix-plugins revert. |
6c0fc2b45e0e3ed4bcaebe22b0b7ecb7e8303da8 isn’t right. (Or rather it’s insufficient.) Edit: Never mind; it’s in the next commit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the nix maintainer team should have consulted for that. Also there is no nix issue for this bug.
Result of 1 package blacklisted:
94 packages built:
|
I think we arrived at the consensus to merge the bump as long as we’re willing to revert if problems crop up again, given the reaction to #335342 (review) and discussion with @fabianhjr on Matrix when they were making the decision to merge. If there are channel‐blocking eval crash issues cropping up even on the small channel I don’t think we should let a delay risk this shipping to the channels before further assessment. |
Filed a proper bug to contain discussion: NixOS/nix#11547 |
First and foremost we shouldn't break users systems, then do the proper communication and triaging. Reverting seems the most important to me for now, no? |
This reverts commit ac849e5. Nix 2.24 segfaults semi-randomly during evaluation on specific configs (?). This commit prepares for another revert, putting the default back to 2.18. Upstream issue: NixOS/nix#11547
This reverts commit 2e702d0. Segfaults during evaluation in yet-to-be-determined circumstances. Investigation is ongoing, reverting for now to be safe. Upstream issue: NixOS/nix#11547
This reverts commit 0291167. To match Nix version revert. See upstream issue: NixOS/nix#11547
24d85d5
to
7d10007
Compare
One last force push to add upstream issue reference to all commits. |
Description of changes
The segfault bug (see #335342) keeps hitting Hydra on unstable-small, so it's likely going to hit a lot of people once it rolls out widely. Let's revert for now, and investigate without time pressure.
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.