Skip to content
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

workflows/eval: add eval summary before requesting reviewers #371528

Merged

Conversation

wolfgangwalther
Copy link
Contributor

This is to ensure that the eval summary is still set as commit status, even when the review requests fail due to too many reviewers.

Noticed by @emilazy in #370995 (comment).

Things done

  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
    • sandbox = relaxed
    • sandbox = true
  • Tested, as applicable:
  • Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
  • Tested basic functionality of all binary files (usually in ./result/bin/)
  • 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
    • (Package updates) Added a release notes entry if the change is major or breaking
    • (Module updates) Added a release notes entry if the change is significant
    • (Module addition) Added a release notes entry if adding a new NixOS module
  • Fits CONTRIBUTING.md.

Add a 👍 reaction to pull requests you find important.

This is to ensure that the eval summary is still set as commit status,
even when the review requests fail due to too many reviewers.
@github-actions github-actions bot added 6.topic: policy discussion 6.topic: continuous integration Affects continuous integration (CI) in Nixpkgs, including Ofborg and GitHub Actions labels Jan 6, 2025
@github-actions github-actions bot added 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin 10.rebuild-linux: 0 This PR does not cause any packages to rebuild on Linux labels Jan 6, 2025
@emilazy
Copy link
Member

emilazy commented Jan 6, 2025

Will this prevent CI from showing up as failed when this happens?

@wolfgangwalther
Copy link
Contributor Author

No, the job is showing as failed on purpose until we implement something better for that - or decide that silently non-failing is the right thing to do. Still working on that.

@infinisil infinisil merged commit bcac8c0 into NixOS:master Jan 6, 2025
23 of 27 checks passed
@emilazy
Copy link
Member

emilazy commented Jan 6, 2025

I think it’s unfortunate that it makes it look like there’s an eval problem with the PR on every treewide. I would prefer the GitHub grey status that ofborg used to use for this.

(It also means I get an email for every merge into staging-next.)

@wolfgangwalther wolfgangwalther deleted the ci-eval-summary-on-failed-review branch January 6, 2025 21:05
@wolfgangwalther
Copy link
Contributor Author

I would prefer the GitHub grey status that ofborg used to use for this.

100%, so would I. Unfortunately - not that easy to do :D

@emilazy
Copy link
Member

emilazy commented Jan 6, 2025

Well, I’d still take green over red if those are the two choices, because of the email thing :)

@infinisil
Copy link
Member

How about continue-on-error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
6.topic: continuous integration Affects continuous integration (CI) in Nixpkgs, including Ofborg and GitHub Actions 6.topic: policy discussion 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin 10.rebuild-linux: 0 This PR does not cause any packages to rebuild on Linux
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants