Repository navigation
Conversation
Upstream runs library tests with retries: process.env.CI ? 3 : 0. Do the same in CI: after the run, re-run only the failed tests, in a fresh test process, up to 3 more times. A test that passes on a retry is listed as flaky and does not fail the job. Local runs are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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
1 participant
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.
Upstream Playwright retries failed library tests up to 3 times on CI (
retries: process.env.CI ? 3 : 0), and that is how it stays green with known browser races. One example is the Chromium WebMCP iframe hang: a child frame'sgetTools()sometimes never resolves, even from plain page JavaScript. CI now does the same. After the normal run, a small script re-runs only the failed tests in a fresh test process, up to 3 more times. A test that passes on a retry is listed as flaky in the log and the job summary, and does not fail the job.The retry happens at the workflow level, not inside NUnit. NUnit allows only one repeat attribute per test, many tests carry two
[PlaywrightTest]attributes, and[Retry]does not cover errors or timeouts. A fresh process also gives each retry a clean SetUp and TearDown, and handles timed-out tests whose TearDown would otherwise run late. Localdotnet testruns are unchanged.🤖 Generated with Claude Code