The WikiLambda extension has been running reliably on the beta cluster for a few months. Recently, for the first time, we added a couple jobs. The jobs are instantiated and pushed onto a job queue group in the normal way. They are working in local dev environments, but apparently are not running at all in our beta deployment. Log statements show the instantiation of these jobs as expected, but log statements from within their run() methods have never appeared.
We have the normal configuration declarations for these jobs are in our extension.json, like this example:
"JobClasses": {
"myExtDoSomething": "MediaWiki\\Extension\\MyExt\\Job\\DoSomethingJob"
},as documented in the Extensions section here.
Steps to replicate the issue (include links if applicable):
- Visit https://wikifunctions.beta.wmflabs.org/wiki/Z10020
- Refresh the page (if it's already in your browser)
- Click on the Details tab
- Notice that the Test cases are running (this always happens, and correctly triggers the instantiation of UpdateImplementationsJob)
- Look at WikiLambda channel on logstash
What happens?:
- Job instantiation gets logged (MediaWiki\Extension\WikiLambda\Jobs\UpdateImplementationsJob::__construct Job created!)
- but job running does not get logged (expected log message : INFO: MediaWiki\Extension\WikiLambda\Jobs\UpdateImplementationsJob::run Job being run!)
- Also expect to see an update in the content of the WikiFunctions page, and this does not happen.
What should have happened instead?:
The last 2 bullets just above should also happen.
Other information :
- Our other job, CacheTesterResultsJob, is also not running.
- Jobs PHP code: UpdateImplementationsJob; CacheTesterResultsJob
- Related to T331259: Investigate why ApiPerformTest cache retrieval has stopped working (nothing cached after an edit)
- Possibly related to T325786: htmlCacheUpdate job not being triggered on beta cluster