You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The public WoA resolver currently exits with a silent assertion failure when a selected run is outside its eligible scope. For example, the resolve-public-build failure in run 41704819123 does not record the API response or identify which condition failed.
Log the public run metadata, the result of every eligibility check, and the commit comparison against main. Ineligible runs now emit a notice and a skip reason in the CI summary, then skip batch selection and private dispatch. The existing eligibility rules remain unchanged; API, parsing, and unexpected script errors still fail with an error annotation containing the script line and exit code.
Exercised 19 simulated scenarios using the actual resolver script, covering eligible runs, queued/failed/cancelled runs, repository/workflow/branch/SHA mismatches, main ancestry, manual lookup, and API failures.
No live private dispatch or GB10 run was launched.
No actionable comments were generated in the recent review.
Summary
Summary by CodeRabbit
Chores
Public build checks now provide clearer failure details and report when a run is skipped because it does not meet eligibility requirements.
Batch selection runs only after a build is confirmed eligible. Comparison results are logged before the existing checks are applied.
The WoA public build workflow now logs resolution details, reports failed eligibility checks, and skips ineligible runs. Batch selection runs only when resolution marks a run eligible.
Changes: WoA public build resolution
Layer / File(s)
Summary
Resolve and report eligibility .github/workflows/woa-main-ci.yml
The resolver logs run metadata and failed eligibility checks. It logs commit comparison results, skips runs that fail eligibility or comparison, and sets eligible=true after successful resolution.
The change makes the public WoA resolver log why a run is skipped and runs batch selection only for eligible runs. The path-suffix concern was checked against real runs and does not apply. No remaining merge-blocking risk is identified.
- [ ] Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Reviewing files that changed from the base of the PR and between 526b119 and 9e77ce8.
Files selected for processing: 1
.github/workflows/woa-main-ci.yml
Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review.
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
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.
The public WoA resolver currently exits with a silent assertion failure when a selected run is outside its eligible scope. For example, the resolve-public-build failure in run 41704819123 does not record the API response or identify which condition failed.
Log the public run metadata, the result of every eligibility check, and the commit comparison against main. Ineligible runs now emit a notice and a skip reason in the CI summary, then skip batch selection and private dispatch. The existing eligibility rules remain unchanged; API, parsing, and unexpected script errors still fail with an error annotation containing the script line and exit code.
Validation:
git diff --checkpassed.