From 153956e458157e44d73efc3dd369699ff20e4d12 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Rados=C5=82aw=20Piliszek?= Date: Fri, 27 May 2022 20:14:26 +0200 Subject: [PATCH] [CI] Nullify attempts Per Clark Boylan's feedback [1], retries cause a retry not only for pre playbook failures but also for cases where Ansible detects network connectivity issues and they are caused by disks getting filled to their fullest. This is an issue we experience that sometimes results in a POST_FAILURE but certain FAILUREs are retried which wastes CI resources. The problematic jobs are ceph jobs. They are to be looked into. Backport to all branches. We can adjust retries for the core jobs that do not exhibit the nasty behaviour but first we can try running without retries to measure the troublesomeness. [1] https://review.opendev.org/c/openstack/kolla-ansible/+/843536 Change-Id: I32fc296083b4881e8f457f4235a32f94ed819d9f --- zuul.d/base.yaml | 1 - 1 file changed, 1 deletion(-) diff --git a/zuul.d/base.yaml b/zuul.d/base.yaml index 76e2b87bf7..bd6c72c227 100644 --- a/zuul.d/base.yaml +++ b/zuul.d/base.yaml @@ -4,7 +4,6 @@ pre-run: tests/pre.yml run: tests/run.yml post-run: tests/post.yml - attempts: 5 timeout: 7200 post-timeout: 1800 required-projects: