https://bugzilla.wikimedia.org/show_bug.cgi?id=48025
--- Comment #3 from Antoine "hashar" Musso <has...@free.fr> --- Tips to investigate: tail -f /var/log/apache2/integration_access.log | grep Python That will show the Zuul requests to Jenkins. The time is when the query started, so any backward time will indicated a query that took a long time. On completion, query send a 302 which in turns triggers a GET from Jenkins. Exemple: 02/May/2013:23:17:53 "POST /ci/job/parsoid-parsertests-run-harder/65/submitDescription 302" 02/May/2013:23:17:53 "GET /ci/job/parsoid-parsertests-run-harder/65/ 200" That one has been fast. Before triggering a job, Zuul attempts to lookup whether the job exist. It does that based on the python-jenkins module which hit an API call which is very slow on our setup. I have overridden the existence check with Gerrit Change #62095. For now it seems Jenkins is more or less working after the last restart. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
