On 10/20/26 7:41 PM, Brian Cain wrote:
On 10/20/2026 6:16 PM, Pierrick Bouvier wrote:
When merging PR on the project, it's possible to observe failures on CI
that can be related to sporadic test failures or infrastructure issues
(pod eviction with Kubernetes). As a result, it adds latency on the
process and workload for our top maintainers.
This patch sets an automatic retry (supported by gitlab out of the box),
so failing jobs are automatically retriggered.
It's important to note that in case there is a real test or build
failure, concerned jobs will run a second time, and fail again. That
said, it happens seldomly since sub maintainers are supposed to test for
this before sending it. Also, the retry is limited to the job that
failed, so it should be cheap in terms of CI minutes.
Will this effectively mask those flaky failures so that no one hears
about them? Is there a way to find out about them with something like a
weekly/monthly digest of failures?
I don't have the exact measure about how many tries on average make sure
CI is pass, so retry twice is just a first attempt.
Out of occasional flaky tests, there are also sporadic infra issues
(related to our usage of Kubernetes).
Regards,
Pierrick
