Last modified: 2012-10-30 22:26:36 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 T43565, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 41565 - REL1_19 tests chokes on parserTests
REL1_19 tests chokes on parserTests
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Continuous integration (Other open bugs)
unspecified
All All
: Unprioritized blocker (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-30 21:50 UTC by Antoine "hashar" Musso (WMF)
Modified: 2012-10-30 22:26 UTC (History)
2 users (show)

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


Attachments

Description Antoine "hashar" Musso (WMF) 2012-10-30 21:50:19 UTC
The REL1_19 parserTests are broken. The very first test takes can take more than two second to startup which make the test to timeout.

Example trouble: https://gerrit.wikimedia.org/r/#/c/30834/

According to my local testing that might be due to the language cache being populated on the first test. The cache needs to be prepopulated before the tests begins.
Comment 1 Antoine "hashar" Musso (WMF) 2012-10-30 21:53:42 UTC
On my laptop using an SSD:

0.2645  30.0M  LocalisationCache::recache writing cache for 'en'
1.3191  41.5M  LocalisationCache::recache finished writing cache for 'en'

A bit more than a second, so if that is being done on the first test, that is definitely the root cause.
Comment 2 Antoine "hashar" Musso (WMF) 2012-10-30 22:11:59 UTC
The workaround is to raise the PHP timeout for parser tests to 10 seconds like we have done in 1.20. Backported the change in REL1_19 with https://gerrit.wikimedia.org/r/#/c/30908/
Comment 3 Antoine "hashar" Musso (WMF) 2012-10-30 22:26:36 UTC
That fixed it :-)

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


Navigation
Links