Closed tomberek closed 2 years ago
Staging is a valid target for a backport, so doesn't seem logical to remove it to me.
Thank you everyone for a wonderful ZHF!
Do we have staging jobsets for 21.11? I don't see them in https://hydra.nixos.org/project/nixpkgs. Iirc, this has been improved in the last release, but maybe it hasn't been documented as part of the release process yet? cc @jonringer
Any chance we can get a final detailed eval report? I'm curious now the deltas are for each platform.
Based on https://hydra.nixos.org/eval/1727142?compare=1718945 https://hydra.nixos.org/eval/1727142?filter=x86_64-linux&compare=1718945
x86_64-linux jobset at 653 182 failing jobs
x86_64-darwin at 1449 1208 failing jobs (some aborted)
aarch64-linux at 782 505 failing jobs
Do we have staging jobsets for 21.11? I don't see them in https://hydra.nixos.org/project/nixpkgs. Iirc, this has been improved in the last release, but maybe it hasn't been documented as part of the release process yet? cc @jonringer
we should
done, just created it, and added notes about its creation to the update wiki PR
Was there supposed to be a pass where (most of) the remains get marked with meta.broken
or similar?
Note there are still a few outstanding unresolved PRs :point_up: #148045 #147405 #147332 #147543 at least
Was there supposed to be a pass where (most of) the remains get marked with
meta.broken
or similar?
This is meant to be done on the release branch, but it is a PITA
cc @nrdxp @tomberek
Mission
Every time we branch off a release we stabilize the release branch. Our goal here is to get as little as possible jobs failing on the trunk/master jobsets. I'd like to heighten, while it's great to focus on zero as our goal, it's essentially to have all deliverables that worked in the previous release work here also.
Please note the changes included in RFC 85.
Most significantly, branch off will occur on 2021 Nov 19; prior to that date, ZHF will be conducted on master; after that date, ZHF will be conducted on the release channel using a backport workflow similar to previous ZHFs.
Jobsets
nixos:release-21.11 Jobset nixpkgs:nixpkgs-21.11-darwin Jobset
How many failing jobs are there?
At the opening of this issue we have
x86_64-linux
jobset at 653 failing jobsx86_64-darwin
at 1449aarch64-linux
at 782Thanks to nix-review-tools we know which dependencies are causing the most jobs to fail in these individual jobsets:
Previous releases first evals
20.09 had 1153 failing jobs 21.05 had 789 failing jobs
How to help (textual)
Select an evaluation of the trunk jobset
Find a failed job ❌️ , you can use the filter field to scope packages to your platform, or search for packages that are relevant to you. Note: you can filter for architecture by filtering for it, eg: https://hydra.nixos.org/eval/1719540?filter=x86_64-linux&compare=1719463&full=#tabs-still-fail
Search to see if a PR is not already open for the package. It there is one, please help review it.
If there is no open PR, troubleshoot why it's failing and fix it.
Create a Pull Request with the fix targeting master, wait for it to be merged. If your PR causes around 500+ rebuilds, it's preferred to target
staging
to avoid compute and storage churn.(after 2021 Nov 19) Please follow backporting steps and target the
release-21.11
branch if the original PR landed inmaster
orstaging-21.11
if the PR landed instaging
. Be sure to dogit cherry-pick -x <rev>
on the commits that landed in unstable. @jonringer created a video covering the backport process.Always reference this issue in the body of your PR:
Please ping @NixOS/nixos-release-managers on the PR. If you're unable to because you're not a member of the NixOS org please ping @jonringer, @tomberek , @nrdxp
How can I easily check packages that I maintain?
You're able to check failing packages that you maintain by running:
New to nixpkgs?
Packages that don't get fixed
The remaining packages will be marked as broken before the release (on the failing platforms). You can do this like:
Closing
This is a great way to help NixOS, and it is a great time for new contributors to start their nixpkgs adventure. :partying_face:
cc @NixOS/nixpkgs-committers @NixOS/nixpkgs-maintainers @NixOS/release-engineers
Related Issues