Last modified: 2014-07-02 10:42:30 UTC
GlobalBlocking is meant to use a dedicated shared database 'globalblocking'. When run under Jenkins harness, we only have one database, whenever another tests hits GlobalBlocking (such as Cite parser tests), we end up with stracktrace because the database load balancer can not find 'globalblocking' database. Luckily: - the GlobalBlocking database can be configured via $wgGlobalBlockingDatabase - Wikimedia Jenkins set $wgWikimediaJenkinsCI So we can just point $wgGlobalBlockingDatabase to $wgDBname. Test case: $ ls extensions Cite GlobalBlocking $ cd tests/phpunit $ php phpunit.php --testsuite extensions
CCed Aude because we used $wgWikimediaJenkinsCI for the Wikibase extension. Blocks Bug 67216 - Have unit tests of all wmf deployed extensions pass when installed together, in both PHP-Zend and HHVM
Change 143253 had a related patch set uploaded by Hashar: Adjust GlobalBlocking database under Wikimedia Jenkins https://gerrit.wikimedia.org/r/143253
Change 143253 merged by jenkins-bot: Adjust GlobalBlocking database under Wikimedia Jenkins https://gerrit.wikimedia.org/r/143253
Needs backport to REL1_23.
Backported.