2a1952d9ba
Why this change? Pull requests can introduce flaky tests into the mix and we do not want to be hiing that during the pull request process. While this does mean builds for PR will be less stable than the `main` branch without retries, we do not foresee this to be a problem long term since the monitoring of flaky tests on the `main` branch will mean that the number of flaky tests will eventually be reduced. What does this change do? 1. Introduce the `DISCOURSE_TURBO_RSPEC_RETRY_AND_LOG_FLAKY_TESTS` env variable which will initialize `TurboTest::Runner` with the `retry_and_log_flaky_tests` kwarg set to true when set. 2. Change the tests workflow run to set `DISCOURSE_TURBO_RSPEC_RETRY_AND_LOG_FLAKY_TESTS` only when the build type is `backend` or `system` and the `github.ref_name` is `main`. |
||
|---|---|---|
| .. | ||
| docker | ||
| annotate | ||
| bundle | ||
| dev | ||
| ember-cli | ||
| notify_file_change | ||
| rails | ||
| rake | ||
| rspec | ||
| rubocop | ||
| system_rspec | ||
| turbo_rspec | ||
| unicorn | ||
| yarn-app | ||