Repository navigation
eden-trusted: retry status API calls - #6940
Merged
Merged
Conversation
eriknordmark
requested review from
rene,
shjala and
yash-zededa
as code owners
October 26, 2026 22:45
The steps that publish Eden results as commit statuses call the GitHub API with no retries, so a single 5xx fails the job. When the per-suite render fails, the previous attempt's statuses stay on the PR, so a suite that passed on re-run still shows failure. The PR then stays red until someone re-runs the job by hand. On one run with several attempts, the jobs listing returned 502 after about 10 s, twice in a row. Retry each status step up to three times. Fetch the job list in pages of 50, so each request is lighter and a run with more than 100 jobs is not silently truncated. Signed-off-by: eriknordmark <erik@zededa.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
eriknordmark
force-pushed
the
eden-status-retries
branch
from
October 28, 2026 23:17
f722594 to
e698ea5
Compare
rene
approved these changes
Oct 29, 2026
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.
Description
The steps in
eden-trusted.ymlthat publish Eden results as commit statusescall the GitHub API with
retries: 0, so a single 5xx fails the job. When"Render each Eden jobs status" fails, the per-suite statuses from the previous
attempt stay on the PR. A suite that passed on re-run then still shows
failure, and the PR stays red until someone re-runs that job by hand. Thishappened on #6875: the jobs listing returned 502 after about 10 s on two
consecutive attempts.
This PR retries each of the three
actions/github-scriptsteps up to threetimes, with back-off at 1 s, 4 s and 9 s. 5xx is not in the default retry-exempt
list. The render step also fetches the job list in pages of 50, so each request
is lighter and a run with more than 100 jobs is no longer truncated.
How to test and validate this PR
This is a CI-only change with nothing to system-test. It cannot be exercised
from its own PR:
PR buildignores.github/**, andRun Edenis aworkflow_runworkflow, so GitHub always runs master's copy. After merge, checkon any PR's
Run Edenrun that "Reset & Render Eden statuses", "Eden TestsComplete" and "Render each Eden jobs status" pass, and that each Eden suite
appears as its own commit status on the PR head.
Changelog notes
None.
PR Backports
Run Edenis triggered byworkflow_run, so PRs against every stable branch runmaster's copy of this workflow.
Checklist
I've provided a proper description
I've added the proper documentation
I've tested my PR on amd64 device
I've tested my PR on arm64 device
I've written the test verification instructions
I've set the proper labels to this PR
I've checked the boxes above, or I've provided a good reason why I didn't
check them. This is a CI workflow change: no documentation or device testing
applies.
🤖 Generated with Claude Code