You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add EMTEST_RETRY_COUNT to force retrying failed tests (#25565)
The way this differs from the existing EMTEST_RETRY_FLAKY is that this
retries any failed test, whereas EMTEST_RETRY_FLAKY only retries those
tests that had explicitly been deemed to be flaky beforehand.
The rationale for adding this feature is twofold:
1. There is currently so much flakiness in tests in the current test
suites, that I would be flagging flaky tests for many months to come in
my own CI. It is unclear if some of that flakiness is a harness problem
or a systemic problem rather than an individual test problem, so I could
end up flagging a majority of all tests in the suites as flaky.
2. Whenever a test fails in my CI, the very first thing I need to check
is whether the failure was just a one-off, or whether the failure was a
deterministic failure. So being able to run with `EMTEST_RETRY_COUNT=5`
will automate such testing for me and immediately give me feedback
whether any test failure was deterministic or intermittent.
0 commit comments