Skip to content

Fix CI checks job to detect test failures#1547

Merged
kkraus14 merged 1 commit intoNVIDIA:mainfrom
kkraus14:fix-ci-checks-failure-detection
Jan 30, 2026
Merged

Fix CI checks job to detect test failures#1547
kkraus14 merged 1 commit intoNVIDIA:mainfrom
kkraus14:fix-ci-checks-failure-detection

Conversation

@kkraus14
Copy link
Collaborator

Summary

  • Fix the checks job to detect test failures, not just cancellations
  • The bug allowed PRs to merge even when tests failed because the checks job only verified result == 'cancelled' but not result == 'failure'

Test plan

  • Verify CI runs and the checks job correctly fails when tests fail

The checks job only verified if jobs were cancelled, but did not check
if they failed. This allowed PRs to merge even when tests failed because
the checks job would exit with 0 (success) when tests had result='failure'.

Add failure checks alongside the existing cancellation checks for all
test jobs and the doc job.
@copy-pr-bot
Copy link
Contributor

copy-pr-bot bot commented Jan 30, 2026

Auto-sync is disabled for ready for review pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

@kkraus14
Copy link
Collaborator Author

/ok to test

@kkraus14 kkraus14 enabled auto-merge (squash) January 30, 2026 16:18
@github-actions

This comment has been minimized.


checks:
name: Check job status
if: always()
Copy link
Contributor

@cpcloud cpcloud Jan 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't remember if this necessary, but what about ${{ !failed() }} here to avoid the extra conditionals?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to block if the job is cancelled as well, so it can't just be !failed()

@kkraus14 kkraus14 merged commit 63b68c1 into NVIDIA:main Jan 30, 2026
86 checks passed
@github-actions
Copy link

Doc Preview CI
Preview removed because the pull request was closed or merged.

@leofang
Copy link
Member

leofang commented Feb 1, 2026

I wonder if we should discuss reverting #1008 and getting back to the old way of gating the checks... This seems error prone and not scalable to me.

kkraus14 added a commit to kkraus14/numba-cuda that referenced this pull request Feb 5, 2026
The `checks` job only checked for `cancelled` dependencies but not
`failure`, meaning a failing CI job would not cause the overall status
check to fail. Add `failure` result checks alongside existing
`cancelled` checks for all dependencies.

Mirrors the fix from NVIDIA/cuda-python#1547.
kkraus14 added a commit to NVIDIA/numba-cuda that referenced this pull request Feb 5, 2026
## Summary

- The `checks` job in `ci-new.yaml` only checked for `cancelled`
dependencies but not `failure`, meaning a failing CI job would not cause
the overall status check to fail.
- Add `failure` result checks alongside existing `cancelled` checks for
all dependencies.

Mirrors the fix from NVIDIA/cuda-python#1547.

## Test plan

- Verify that the `checks` job now correctly reports failure when any
dependency job fails (not just when cancelled).

---------

Co-authored-by: Graham Markall <gmarkall@nvidia.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants