Page MenuHomePhabricator

GlobalBlocking cause other extensions tests to fail (globalblocking database not found)
Closed, ResolvedPublic

Description

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


Version: unspecified
Severity: normal

Details

Reference
bz67353

Event Timeline

bzimport raised the priority of this task from to High.Nov 22 2014, 3:40 AM
bzimport set Reference to bz67353.
bzimport added a subscriber: Unknown Object (MLST).
hashar created this task.Jul 1 2014, 8:22 AM
hashar added a comment.Jul 1 2014, 8:23 AM

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.