Skip to content

Retry fork CI job listings in smaller pages - #76327

Merged
shahar1 merged 1 commit into
mainfrom
fork-ci-jobs-smaller-pages
Nov 3, 2026
Merged

shahar1 merged 1 commit into
mainfrom
fork-ci-jobs-smaller-pages

Conversation

@potiuk

@potiuk potiuk commented Nov 2, 2026

Copy link
Copy Markdown
Member

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.

  • Fork run jobs are listed 100 per page first. If GitHub keeps answering with server errors, the listing is tried again at 30, 15 and then 5 per page.
  • Only server errors drop to the shorter attempt count. Rate limits and connection errors are still retried the full four times.

Was generative AI tooling used to co-author this PR?
  • Yes — Claude Code (Claude Opus 5)

Generated-by: Claude Code (Claude Opus 5) following the guidelines

🤖 Generated with Claude Code

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
@shahar1
shahar1 merged commit 8693c08 into main Nov 3, 2026
172 checks passed
@shahar1
shahar1 deleted the fork-ci-jobs-smaller-pages branch November 3, 2026 12:57
@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

Backport successfully created: v3-4-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
✅ v3-4-test PR Link

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
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants