fix(ci): make ci-status wait for flaky test re-runs#6079
Open
leseb wants to merge 1 commit into
Open
Conversation
…g immediately When a CI check fails, ci-status now keeps polling instead of immediately concluding with failure. This allows re-running just the flaky job without also having to restart ci-status. The timeout is increased from 60 to 180 minutes to accommodate re-run wait times. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Sébastien Han <seb@redhat.com>
leseb
requested review from
bbrowning,
cdoern,
franciscojavierarceo,
mattf,
raghotham and
skamenan7
as code owners
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Makes the
ci-statusaggregator job wait indefinitely (up to the 3-hour timeout) for failed checks to be re-run, instead of failing immediately when it sees a failure. This means you only need to restart the flaky job itself, not both the flaky job andci-status.Before: A flaky test fails ->
ci-statusimmediately fails -> you restart the flaky job ANDci-status.After: A flaky test fails ->
ci-statuskeeps polling -> you restart just the flaky job ->ci-statuspicks up the green result automatically.Changes:
core.error+core.setFailed+returnwithcore.warning+continueso the polling loop keeps runningTest Plan
ci-statuslogs warnings but keeps pollingci-statusdetects the re-run and eventually reports success