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
It would be nice if at a regular interval (let's say every monday at 3 UTC) a CI job would run with -count=25 or something else dumb like this.
And report any new flaky failure. It would force us to not have any flake test.
The text was updated successfully, but these errors were encountered:
An alternative could be something like golang's watchflake, where a bot would notice runs that failed were restarted and then sucesfully completed, and open an issues for theses.
We could also use monkeybrains to do that, forcing us to report any flake that happened if we reran a test.
It would be nice if at a regular interval (let's say every monday at 3 UTC) a CI job would run with
-count=25
or something else dumb like this.And report any new flaky failure. It would force us to not have any flake test.
The text was updated successfully, but these errors were encountered: