Skip to content

Retry transient Bazel download failures in downstream tests - #960

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

RolandJentschETAS with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-downstream-test-job

Conversation

Copilot AI commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor

📌 Description

The downstream compatibility job failed when Bazel’s download of rules_py received HTTP 500 from GitHub. This change retries Bazel commands on HTTP 5xx download failures, while other command failures remain immediate.

  • Retry policy: Allow up to three attempts with backoff for transient HTTP 5xx download errors.
  • Regression test: Verify a failed download is retried and the command succeeds on a subsequent attempt.

🚨 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

Co-authored-by: RolandJentschETAS <135332348+RolandJentschETAS@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix failing GitHub Actions job downstream compatibility Retry transient Bazel download failures in downstream tests 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