Last modified: 2014-11-17 21:36:12 UTC
After running tests, job queue gets overflown by jobs spawned by test data creation, which due to job runner, results in one process consistently eating one CPU core: www-data 28814 95.6 5.1 758568 106112 ? RN 22:17 0:02 php maintenance/runJobs.php --wiki=wiki-unittest_ --type=cirrusSearchLinksUpdateSecondary --maxt Which noticeably heats up my laptop and reduces battery time. The temporary solution is echo flushall|redis-cli && sudo pkill -e -9 php however a proper fix is needed.
(In reply to Max Semenik from comment #0) > The temporary solution is > echo flushall|redis-cli && sudo pkill -e -9 php > however a proper fix is needed. Like tests not leaving bogus jobs around? Or is this caused by the phpunit environment picking up the "production" MW configuration? I know I needed to add a settings file to set `if ( defined( 'MW_PHPUNIT_TEST' ) ) { $wgSharedDB = null; }` because of the centralauth role making phpunit barf. Maybe there is a set of similar settings that should be put into LocalSettings.php for MW-V?
Bulk unassigning bugs from Ori.
