Last modified: 2008-12-02 18:22:00 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 T18374, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 16374 - parserTests.php always assumes $wgDBprefix is 'parsertest_'
parserTests.php always assumes $wgDBprefix is 'parsertest_'
Status: RESOLVED DUPLICATE of bug 15892
Product: MediaWiki
Classification: Unclassified
Maintenance scripts (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-11-17 21:39 UTC by Siebrand Mazeland
Modified: 2008-12-02 18:22 UTC (History)
2 users (show)

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


Attachments

Description Siebrand Mazeland 2008-11-17 21:39:47 UTC
parserTests.php always assumes $wgDBprefix is 'parsertest_'. Without making a change in parserTests.inc line 540 ('wgDBprefix' => 'parsertest_') this would never run succesfully and exit with something like "Error: 1146 Table 'mediawiki.parsertest_objectcache' doesn't exist (localhost)".

I suggest that a commandline option is added to change the used database prefix, with a special case for when no prefix is used.
Comment 1 Brion Vibber 2008-11-17 22:05:30 UTC
The prefix for the test database *is* 'parsertest_'; this is correct.

I assume you're referring to the problem where the objectcache is pulling things incorrectly when not fully set up?
Comment 2 Siebrand Mazeland 2008-11-17 22:09:19 UTC
There is little to no documentation I could find on running parser tests. Do I assume correctly that you mean that a database prefix of 'parsertest_' is *required* for properly running parser tests?
Comment 3 Chad H. 2008-11-25 20:39:33 UTC
Cf: r43943
Comment 4 Ilmari Karonen 2008-12-02 18:22:00 UTC
I think this is a duplicate of bug 15892, and should be fixed (though inelegantly) by r44003.

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

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


Navigation
Links