-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
packaging: move tests to passthru #12063
Conversation
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.
The VM tests already run with
nix.package = nixpkgsFor.${system}.native.nixComponents.nix-cli;
and nix-cli
does not include tests.
(It's an input to everything.nix
, not its return value)
Another possibility would be to override the doCheck
and doInstallCheck
attrs to false
where desired.
I don't think we should do this before we have something like
They still seem to build all those tests for some reasons. Why do we need to define tests as check inputs? I don't see the advantage. If someone wants to do |
@mergify queue |
🛑 The pull request has been synchronized by a user |
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/2024-12-16-nix-team-meeting-minutes-203/57483/1 |
@mergify rebase |
✅ Branch has been successfully rebased |
Motivation
This is unnecessary build tests in some builds, where we don't actually need it.It is useful to build nix without having to run tests.
Before when running vm tests we were also building unittests.
Context
Add 👍 to pull requests you find important.
The Nix maintainer team uses a GitHub project board to schedule and track reviews.