Lix 2.92.0 deadlocks during substitution #745
Labels
No labels
Affects/CppNix
Affects/Nightly
Affects/Only nightly
Affects/Stable
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/lix ci
Area/nix-eval-jobs
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/repl/debugger
Area/store
bug
Context
contributors
Context
drive-by
Context
maintainers
Context
RFD
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
imported
Language/Bash
Language/C++
Language/NixLang
Language/Python
Language/Rust
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
Topic/Large Scale Installations
ux
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#745
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Describe the bug
A clear and concise description of what the bug is.
If you have a problem with a specific package or NixOS,
you probably want to file an issue at https://github.com/NixOS/nixpkgs/issues.
Steps To Reproduce
???
deadlock
Expected behavior
A clear and concise description of what you expected to happen.
nix --version
output2.92.0
Additional context
And
Triggered this by
C-c
'ing a slow substitutionyou're obviously running something pre
ec44c8bd6c
, judging byPathLocks::lockPaths
appearing in the traces above despite this function having been gone for over a month. those versions did have locking bugs that would cause things to get stuck like this (eg #613). next time please fill in the report fully, okay?Yeh this is 2.92.0. i dont know how to run master.
Updated to add that info.
Lix deadlocks during substitutionto Lix 2.92.x deadlocks during substitutionLix 2.92.x deadlocks during substitutionto Lix 2.92.0 deadlocks during substitutionhas this happened any more since? we haven't seen any deadlocks in a long time and would thus consider this problem to be solved