On 10/20/2026 4: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. > > Signed-off-by: Pierrick Bouvier <[email protected]> > --- > .gitlab-ci.d/base.yml | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/.gitlab-ci.d/base.yml b/.gitlab-ci.d/base.yml > index 8fe00809357..63ba82e3632 100644 > --- a/.gitlab-ci.d/base.yml > +++ b/.gitlab-ci.d/base.yml > @@ -31,8 +31,9 @@ variables: > # Ensure docker.py / tests/docker/Makefile.include always displays stdout > # from any docker commands to aid debugging of failures > DOCKER_V: 1 > - > interruptible: true > + # automatic retry on failure (sporadic test failures or infra issues) > + retry: 2 > > rules: > #############################################################
This was merged into master (3ad81d3d271cef6ce95b3a3a33bb71faabef56a2). First pipeline was green without requiring a manual retry: https://lore.kernel.org/qemu-devel/[email protected]/T/#md488890f5d439b02b5da24d7770e71f7e6283390 Regards, Pierrick
