Last modified: 2012-11-05 21:25:27 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T43657, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 41657 - Jenkins job "MediaWiki-Tests-Parser" should not be timing out randomly
Jenkins job "MediaWiki-Tests-Parser" should not be timing out randomly
Status: RESOLVED DUPLICATE of bug 41607
Product: Wikimedia
Classification: Unclassified
Continuous integration (Other open bugs)
unspecified
All All
: High critical (vote)
: ---
Assigned To: Antoine "hashar" Musso (WMF)
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-11-01 19:58 UTC by Krinkle
Modified: 2012-11-05 21:25 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Krinkle 2012-11-01 19:58:08 UTC
Another one:

https://integration.mediawiki.org/ci/job/MediaWiki-Tests-Parser/8456/testReport/(root)/ParserTests__testParserTest/testParserTest_with_data_set__0/

Caused https://gerrit.wikimedia.org/r/#/c/31290/ to be marked failure incorrectly.

We should look into extending the timeout of 10 seconds or making the test faster.
Comment 1 Antoine "hashar" Musso (WMF) 2012-11-05 21:25:27 UTC
The only tests that deserves 10 a seconds timeout are the one doing heavy database access / refreshing the l10n cache and that sort of thing.  I have even seen a Parser test reaching the 10 seconds timeout :(

The test slowness is a side effect of the upgrade of our continuous integration server from Lucid to Precise. Apparently caused by disk slowness. That is tracked with bug 41607 which make this one a duplicate.

*** This bug has been marked as a duplicate of bug 41607 ***

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links