Repository navigation
Retry fork CI job listings in smaller pages - #76327
Merged
Merged
Conversation
GitHub answers HTTP 502 on every attempt when it lists 100 jobs per page of some large fork runs that were re-run, while smaller pages of the same run list fine. The fork CI monitor then never read the re-run's jobs, so job statuses of the failed first attempt stayed red on the pull request after the re-run passed, as on #74696. Generated-by: Claude Opus 5
potiuk
requested review from
amoghrajesh,
bugraoz93,
choo121600,
ephraimbuddy,
jason810496,
jedcunningham,
jscheffl and
vatsrahul1001
as code owners
November 2, 2026 20:41
shahar1
approved these changes
Nov 3, 2026
Contributor
Backport successfully created: v3-4-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
Merged
1 task done
vatsrahul1001
pushed a commit
that referenced
this pull request
Nov 4, 2026
GitHub answers HTTP 502 on every attempt when it lists 100 jobs per page of some large fork runs that were re-run, while smaller pages of the same run list fine. The fork CI monitor then never read the re-run's jobs, so job statuses of the failed first attempt stayed red on the pull request after the re-run passed, as on #74696. (cherry picked from commit 8693c08) Co-authored-by: Jarek Potiuk <jarek@potiuk.com> Generated-by: Claude Opus 5
shahar1
pushed a commit
that referenced
this pull request
Nov 6, 2026
GitHub answers HTTP 502 on every attempt when it lists 100 jobs per page of some large fork runs that were re-run, while smaller pages of the same run list fine. The fork CI monitor then never read the re-run's jobs, so job statuses of the failed first attempt stayed red on the pull request after the re-run passed, as on #74696. (cherry picked from commit 8693c08) Co-authored-by: Jarek Potiuk <jarek@potiuk.com> Generated-by: Claude Opus 5
vatsrahul1001
pushed a commit
that referenced
this pull request
Nov 9, 2026
GitHub answers HTTP 502 on every attempt when it lists 100 jobs per page of some large fork runs that were re-run, while smaller pages of the same run list fine. The fork CI monitor then never read the re-run's jobs, so job statuses of the failed first attempt stayed red on the pull request after the re-run passed, as on #74696. (cherry picked from commit 8693c08) Co-authored-by: Jarek Potiuk <jarek@potiuk.com> Generated-by: Claude Opus 5
1 task done
potiuk
added a commit
that referenced
this pull request
Nov 15, 2026
* [v3-4-test] Sync fork CI changes from main Several fork CI changes merged to main since the last sync never reached v3-4-test, and the fork CI monitor reads the gate configuration of a pull request's base branch, so pull requests to v3-4-test were still closed after 7 days and missed ten pilot participants. The fork CI modules, their tests, the design document and its diagrams, the monitor workflow, the gate configuration checks and the contributor documentation now match main, taking in #75814, #75696, #76272, #76316, #76327, #76510, #76538, #76677, #76681, #76835, #76836, #76837, #76839, #76841, #76866, #76267 and #77100. The pilot participants new to this branch join at 2026-11-16 00:00 UTC rather than at their main dates, as the gate configuration check requires a future instant for an entry that is new on the base branch. Generated-by: Claude Opus 5 * [v3-4-test] Say the fork CI monitor runs every 5 minutes in the CI tasks doc The sentence changed with #76836 on main and was missed by the sync. Generated-by: Claude Opus 5 * [v3-4-test] Bring the fork CI GitHub client tests in line with main The tests for the smaller job listing pages (#76327) were missed by the sync; the client code they cover is already in it. Generated-by: Claude Opus 5
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
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.
GitHub answers HTTP 502 on every attempt when it lists 100 jobs per page of some large fork runs that were re-run, while smaller pages of the same run list fine. The fork CI monitor then never read the re-run's jobs, so the job statuses of a failed first attempt stayed red on the pull request after the re-run passed. #74696 shows this: its fork run has 275 jobs over 3 attempts, and its
Fork CI job / …statuses still show the attempt-1 failures, while the "Could not classify or update … HTTP 502" Slack alerts repeat.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Claude Opus 5) following the guidelines
🤖 Generated with Claude Code