-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Manifest generation seems stuck possibly because current generation code breaks #5
Comments
Reading this again, I see something that i missed last time. First, the /nix/sources.json is a bit old. But that's not really a problem. I mentioned The actual problems are that current upstream builds are failing (unstable [1], 22.05 It'd be nice if the hydra query [4] could actually filter on the evaluation build status Any thoughts on that ^? [1] On unstable, commit 2001e2b31c565bcdf7bc13062b8d7cfccaca05b8, there is a typoed
[2] For the release-22.05, commit c132d0837dfb9035701dcd8fc91786c605c855c3, it's yet
[3] Same goes for release-21.11, commit eabc38219184cc3e04a974fe31857d8e0eac098d
[4] https://github.com/nix-community/nixpkgs-swh/blob/master/scripts/generate.sh#L19-L22 [5] It seems to be in failure in all versions i've checked afaiui... https://hydra.nixos.org/jobset/nixos/release-21.11/evals?page=1 Cheers, |
fixed those 2 eval errors, lmk if there's more |
I started to open a few PRs in order to fix the eval issues:
Also noted the following issues:
|
The README mentions "The nix-community Buildkite CI generates it each day by picking a
Nixpkgs commit built by Hydra". But the last commit referenced from the main page [1]
dates back from october 11th 2021 [2].
Trying to trigger locally the generation ends up with failures. Be it testing with the
"unstable" release [3] or the current latest release "22.05" [4].
I was hoping to have a look and understand how to fix either #1 or #4 but i'm stuck now.
Any idea how to fix this, please?
Cheers,
[1] https://nix-community.github.io/nixpkgs-swh/
[2] https://github.com/NixOS/nixpkgs/tree/e4ef597edfd8a0ba5f12362932fc9b1dd01a0aef
[3]
[4]
The text was updated successfully, but these errors were encountered: