summaryrefslogtreecommitdiff
path: root/.zuul.yaml
diff options
context:
space:
mode:
authorTobias Henkel <tobias.henkel@bmw.de>2019-05-17 10:21:48 +0200
committerTobias Henkel <tobias.henkel@bmw.de>2019-05-17 10:21:48 +0200
commitd3015e82726a6a4abc535c13cbf0f83355b5678d (patch)
tree48da749063ecd25208432b0182e421e61bc5946f /.zuul.yaml
parent91663cd23813f394cf14244cbcc95aa250039731 (diff)
downloadzuul-d3015e82726a6a4abc535c13cbf0f83355b5678d.tar.gz
Increase timeout of zuul-tox-remote
We frequently have runtimes of zuul-tox-remote near the default timeout of 30 minutes and also see occasional timeouts on slower nodes. Thus increase the timeout to 45 minutes. Change-Id: I97f29ff781d6bb087346e09df7f3328ca9e5f572
Diffstat (limited to '.zuul.yaml')
-rw-r--r--.zuul.yaml6
1 files changed, 4 insertions, 2 deletions
diff --git a/.zuul.yaml b/.zuul.yaml
index a2b230ddd..a9c69a37e 100644
--- a/.zuul.yaml
+++ b/.zuul.yaml
@@ -194,7 +194,8 @@
- zuul-stream-functional-2.6
- zuul-stream-functional-2.7
- zuul-stream-functional-2.8
- - zuul-tox-remote
+ - zuul-tox-remote:
+ timeout: 2700 # 45 minutes
- zuul-quick-start:
dependencies: zuul-build-image
- nodepool-zuul-functional:
@@ -231,7 +232,8 @@
- zuul-stream-functional-2.6
- zuul-stream-functional-2.7
- zuul-stream-functional-2.8
- - zuul-tox-remote
+ - zuul-tox-remote:
+ timeout: 2700 # 45 minutes
- zuul-quick-start:
dependencies: zuul-upload-image
post: