nix flake check --no-build fails on flake dependencies #587
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
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#587
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
nix flake check --no-build
fails if flake dependencies used during evaluation are not present in the store.Steps To Reproduce
nix flake check --no-build
Expected behavior
--no-build
should avoid building actual derivations, but should fetch flake dependencies if required.nix --version
outputAdditional context
My goal is to implement different steps for evaluation checks and build checks in CI. If anyone knows of a simple workaround to fetch required dependencies before the check let me know.
So I checked the source code, and this simple change in lix/nix/flake.cc did the trick:
Now I am not sure what the intention of this code was, but it does not make sense for me to not build any derivations during check, including flake dependencies.
--no-build
still avoids building check dependencies as intendeded (see line 803)