| Cirdan | |
| Apr 26 2019, 3:49 PM |
| F28790170: grafik.png | |
| Apr 26 2019, 3:49 PM |
There is a larger number (currently 14) jobs waiting in the queue. If I recall correctly, the FARotBot job has been stuck for over a week already.
(I would at least like to understand why the job workers get stuck while the "regular" wiki workers seem to be running fine.)
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Cyberpower678 | T221971 IABot job queue has been stuck for days | |||
| Resolved | Cyberpower678 | T269831 IABot job queue has been stuck for a long time |
I wonder if this task should be higher priority as this is imho a core feature of the bot..
@Zppix Cyberpower678 is the only developer and operator/maintainer of the bot, hence the prioritization is rarely used within the InternetArchiveBot Phabricator project, quite often task are never triaged at all. You can be sure that he is working towards resolving all issues around the bot as often as his time permits.
There are internal issues with the workers causing them to hang. I've been pushing them along a bit. The queue is almost cleared now.
see https://tools.wmflabs.org/iabot/index.php?page=viewjob&id=3908
, bot is still stocked.
There are currently 46 jobs in the queue. The bot will get to them eventually, but as far as I know there are some serious issues with the job workers, requiring manual intervention by the bot's developer on a regular basis.