Page MenuHomePhabricator

[Task] Investigate why QUnit jobs time out randomly
Closed, DuplicatePublic

Description

Typical example from https://integration.wikimedia.org/ci/job/mwext-qunit-composer/3296/console:

…
11:32:26 Chromium 50.0.2661 (Ubuntu 0.0.0): Executed 1363 of 1363 SUCCESS (0 secs / 26.499 secs)
11:32:26 Chromium 50.0.2661 (Ubuntu 0.0.0): Executed 1363 of 1363 SUCCESS (26.9 secs / 26.499 secs)
11:32:26 26 05 2016 11:32:26.766:DEBUG [karma]: Run complete, exiting.
11:32:26 26 05 2016 11:32:26.767:DEBUG [launcher]: Disconnecting all browsers
11:59:51 Build timed out (after 30 minutes). Marking the build as failed.
11:59:51 Build was aborted
…

This happens almost every day now, "randomly", on several extensions (e.g. Wikibase and ArticlePlaceholder). A "recheck" usually makes the issue disappear, with no change. Actual issues with that include:

  • Gerrit patches are blocked for more than 30 minutes (see mwext-qunit-composer FAILURE in 30m 00s in https://gerrit.wikimedia.org/r/290431 for an example).
  • Wastes developers time.
  • Not sure what CPU resources this wastes. Hopefully none.

Event Timeline

Restricted Application added subscribers: Zppix, Aklapper. · View Herald TranscriptMay 26 2016, 1:43 PM
thiemowmde triaged this task as Medium priority.May 26 2016, 1:44 PM
JanZerebecki renamed this task from [Task] Investigate why QUnit tests time out randomly to [Task] Investigate why QUnit jobs time out randomly.May 26 2016, 3:00 PM
JanZerebecki added a subscriber: hashar.

Hi yes @hashar tried looking into this but thinks it may be up to the recent karma update in mw core or it is the chrome update we did. I proposed we update to chrome 51 since 50 for me was also unstable.

hoo moved this task from Incoming to Done on the ArticlePlaceholder board.Jun 9 2016, 7:39 PM