-
-
Notifications
You must be signed in to change notification settings - Fork 15.1k
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
When updating nixpkgs-check-by-name
, it should be run on Nixpkgs
#256789
Comments
OfBorg performs checkouts all the time. I don't think this is significant. To run it locally, this style of test runner is not great, but we can refer readers to the instructions for a manual run. |
It's not just a local checkout though, if we use derivations to run the check, then Nixpkgs also needs to be copied into the store. Should probably be fine though, other parts of Nixpkgs also copy Nixpkgs into the store. |
I don't think this should be done after all. With the latest idea here, the latest version of the tooling in Nixpkgs needs to stay independent of the pinned version used for CI. |
Agree that for the PR checking, the currently implemented approach is fine. However, I think it is still good to have the "simple" version that doesn't refer to other Nixpkgs / channels as a The point of this is not to catch CIs, but to just sanity check with hydra after the fact that everything worked out the way it should. The impure tricky business with channels is still necessary, but the idea is that it is an optimization and the simple self-contained |
Implemented in #256789, turns out this would've been really useful 😅 |
When the
nixpkgs-check-by-name
tooling is updated, it should be run on Nixpkgs in the same PR. This also relates to #256788.This could be achieved using
passthru.tests
on thetests.nixpkgs-check-by-name
derivation which copies Nixpkgs to the store and then runs the tooling on it in a derivation. This would then automatically be run when a commit with thetests.nixpkgs-check-by-name:
prefix is in the PR. This is however fairly slow and expensive due to the Nixpkgs copy.The text was updated successfully, but these errors were encountered: