Skip to content

Retry transient downstream repository download failures - #959

Draft
RolandJentschETAS with Copilot wants to merge 3 commits into
mainfrom
copilot/fix-downstream-test-failure
Draft

RolandJentschETAS with Copilot wants to merge 3 commits into
mainfrom
copilot/fix-downstream-test-failure

Conversation

Copilot AI commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor

The lifecycle remote downstream build failed after Bazel received HTTP 500 fetching rules_go v0.60.0. This change retries once for repository download HTTP 5xx failures while preserving immediate failure for other build errors.

  • Retry policy: Retry a failed Bazel command once only when its output reports a repository download HTTP 5xx.
  • Coverage: Add focused tests for the retry and for immediate failure on ordinary build errors.
if "Download from " in line and re.search(r"GET returned 5\d{2}", line):
    retryable_download_error = True

🚨 Impact Analysis

  • This change does not violate any tool requirements and is covered by existing tool requirements
  • This change does not violate any design decisions
  • Otherwise I have created a ticket for new tool qualification

✅ Checklist

  • Added/updated documentation for new or changed features
  • Added/updated tests to cover the changes
  • Followed project coding standards and guidelines

Copilot AI and others added 2 commits October 14, 2026 14:35
Co-authored-by: RolandJentschETAS <135332348+RolandJentschETAS@users.noreply.github.com>
Co-authored-by: RolandJentschETAS <135332348+RolandJentschETAS@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix downstream compatibility job failure in GitHub Actions Retry transient downstream repository download failures Oct 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants