Page MenuHomePhabricator

SpecialPageFatalTest::testSpecialPageDoesNotFatal with data set "ContentTranslationStats"
Closed, ResolvedPublic

Description

It seems b50c884 has caused or exposed a fatal error in MediaWiki core that affects ContentTranslation as can be seen in https://integration.wikimedia.org/ci/job/quibble-vendor-mysql-php70-docker/7190/console:

1) SpecialPageFatalTest::testSpecialPageDoesNotFatal with data set "ContentTranslationStats" (SpecialContentTranslationStats Object (...))
Error: Call to a member function getPrefixedDBkey() on null

/workspace/src/includes/skins/SkinTemplate.php:181
/workspace/src/includes/skins/SkinTemplate.php:539
/workspace/src/extensions/ContentTranslation/specials/ContentTranslationSpecialPage.php:81
/workspace/src/extensions/ContentTranslation/specials/ContentTranslationSpecialPage.php:53
/workspace/src/tests/phpunit/includes/specials/SpecialPageExecutor.php:105
/workspace/src/tests/phpunit/includes/specials/SpecialPageExecutor.php:36
/workspace/src/tests/phpunit/structure/SpecialPageFatalTest.php:41
/workspace/src/tests/phpunit/MediaWikiTestCase.php:469
/workspace/src/maintenance/doMaintenance.php:94

It feels as if the title for the request context is not set properly.

Event Timeline

Change 449436 had a related patch set uploaded (by Addshore; owner: Addshore):
[mediawiki/core@master] SpecialPageExecutor, make sure Skin context is correctly set

https://gerrit.wikimedia.org/r/449436

Addshore moved this task from Unsorted 💣 to Active 🚁 on the User-Addshore board.

As ContentTranslation is a wmf deployed extension, perhaps it should be loaded while the core CI runs?

@hashar, thoughts?

Change 449418 had a related patch set uploaded (by Nikerabbit; owner: Nikerabbit):
[mediawiki/extensions/ContentTranslation@master] DNM Testing T200771

https://gerrit.wikimedia.org/r/449418

Change 449436 merged by jenkins-bot:
[mediawiki/core@master] SpecialPageExecutor, make sure Skin context is correctly set

https://gerrit.wikimedia.org/r/449436

Legoktm subscribed.

I assume this is fixed now.