Just a note - we don't need an increased timeout, if we deploy newer
python-yamlish. That could have been done a long time ago, but we forgot to
update the spec file, so nobody found out. That's why I tried to fix it in
https://phab.qadevel.cloud.fedoraproject.org/D337 . Once that is accepted, the
next libtaskotron build will require the newer python-yamlish.
----- Forwarded Message -----
From: "Tim Flink" <tfl...@redhat.com>
To: infrastruct...@lists.fedoraproject.org
Sent: Thursday, April 9, 2015 11:42:43 PM
Subject: Freeze Break Request: Increase execution timeouts in taskotron's
buildbot
As the set of packages in f22 has grown with freeze, some of the tasks
(most often depcheck) are not completing before hitting the default
timeout of 20 minutes for execution in buildbot.
I want to double the timeout for task execution from 20 to 40 minutes.
I've made the change in dev and stg already and the change works - long
tasks are no longer being killed prior to completion. This freeze break
is for production.
+1s?
Tim
diff --git
a/roles/taskotron/buildmaster-configure/templates/taskotron.master.cfg.j2
b/roles/taskotron/bu
index d7a698f..1a63b0e 100644
--- a/roles/taskotron/buildmaster-configure/templates/taskotron.master.cfg.j2
+++ b/roles/taskotron/buildmaster-configure/templates/taskotron.master.cfg.j2
@@ -175,9 +175,7 @@ factory.addStep(ShellCommand(command=["runtask",
Interpolate('%(prop:taskname)s.yml')],
descriptionDone=[Interpolate('%(prop:taskname)s
on %(prop:item)s')],
name='runtask',
-{% if deployment_type in ['dev', 'stg'] %}
timeout=2400,
-{% endif %}
logfiles={'taskotron.log': {'filename':
'/var/log/taskotron/taskotron.log',
_______________________________________________
infrastructure mailing list
infrastruct...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
_______________________________________________
qa-devel mailing list
qa-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/qa-devel
