Auto-rerun transient Docker startup failures in .NET CI#1360
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/CommunityToolkit/Aspire/main/eng/scripts/dogfood-pr.sh | bash -s -- 1360Or
iex "& { $(irm https://raw.githubusercontent.com/CommunityToolkit/Aspire/main/eng/scripts/dogfood-pr.ps1) } 1360" |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds a GitHub Actions workflow that automatically reruns only those failed .NET CI jobs whose failure matches known transient Docker-startup issues, reducing manual intervention and CI noise for PRs.
Changes:
- Introduces a new
workflow_run-triggered workflow that listens for completed.NET CIruns and inspects failed jobs. - Reruns only failed jobs that match either a failed “Verify Docker is running” step or a port-binding “address already in use” signature during setup.
- Guards against retry loops by only acting on the first run attempt (
run_attempt == 1).
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/auto-rerun-transient-failures.yml | New automation workflow to selectively rerun failed .NET CI jobs when failures match transient Docker startup signatures. |
Copilot's findings
- Files reviewed: 1/1 changed files
- Comments generated: 1
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
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.
N/A
Adds an automated recovery path for transient GitHub Actions failures in PR runs where Docker startup is the root cause.
A new workflow listens for completed
.NET CIruns and selectively reruns only failed jobs when they match known transient Docker signatures:Verify Docker is runningfailedSetup Runtimes, Caching, and Toolsfailed withfailed to bind host port ... address already in useTo avoid retry loops and preserve signal for legitimate failures, reruns are limited to the first attempt only (
run_attempt == 1) and non-matching failures are skipped.PR Checklist
Other information
This change is intentionally narrow so it does not rerun all failed jobs. It only retries jobs with the two Docker-related transient failure patterns observed in recent CI failures.