Last modified: 2012-12-09 12:32:33 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 T28487, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 26487 - parserTests setting its own messages fail on wfMsg
parserTests setting its own messages fail on wfMsg
Status: NEW
Product: MediaWiki
Classification: Unclassified
Unit tests (Other open bugs)
1.18.x
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: i18n
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-12-29 23:00 UTC by Platonides
Modified: 2012-12-09 12:32 UTC (History)
8 users (show)

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


Attachments

Description Platonides 2010-12-29 23:00:14 UTC
Steps to reproduce:
* Set $wgLanguageCode to something other than en in your LocalSettings (yes, parserTests will change to use the English messages)
* Remove 'my_wiki-parsertest_:messages:en' from your "normal" objectcache, eg. DELETE FROM objectcache WHERE keyname = 'my_wiki-parsertest_:messages:en';

(it is loaded from there before the parsertests switches tables)

Run he parser tests
The following parser tests set its own MediaWiki article, and will fail.
* Bad images - basic functionality...
* Bad images - bug 16039: text after bad image disappears...
* <ref> with custom group link..

However, changing $wgLanguageCode to en, and running fixes it for as long as the cache is saved.
Seems that it isn't saved, there's something wrong with its cache...
Comment 1 Niklas Laxström 2011-01-09 11:13:12 UTC
Parser tests should clear the message cache before every test, otherwise the messages added by tests are not picked up.
Comment 2 Siebrand Mazeland 2011-09-12 12:55:34 UTC
All tests that use the i18n system should rebuild L10n cache for the languages that they will be using. Needs some thought, but is probably doable. Any volunteers?

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


Navigation
Links