Last modified: 2012-12-03 17:49:49 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T11520, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 9520 - Job queue never empty.
Job queue never empty.
Status: RESOLVED DUPLICATE of bug 9518
Product: Wikimedia
Classification: Unclassified
Site requests (Other open bugs)
Other All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-04-07 10:49 UTC by Purodha Blissenbach
Modified: 2012-12-03 17:49 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Purodha Blissenbach 2007-04-07 10:49:34 UTC
There seems to be something filling the job queue in a loop, 
we see in pretty quick succession:
    3  (sometimes)
... etc.

If this is caused by possibly recursive behaviour in template 
calls, it was likely introduced - or stirred into the job 
queue - with changes made during the recent days, i.e. most 
likely on or after April, 4th., when I altered inside a system 
of interdependent templates which I mostly did not write or 
design, and at best partially understand. I tried to simplify 
them using parser functions now instead of highly complicated 
other contition-evaluating templates of the pre-parser-
function era.
I remember, I had inspected the job queue after such a change 
and saw it go down to zero, but frankly cannot recall when.
Comment 1 Rob Church 2007-04-07 10:56:26 UTC

*** This bug has been marked as a duplicate of 9518 ***
Comment 2 Andre Klapper 2012-12-03 13:59:38 UTC
[mass-moving wikistats reports from Wikimedia→Statistics to Analytics→Wikistats to have stats issues under one Bugzilla product (see bug 42088) - sorry for the bugspam!]

Note You need to log in before you can comment on or make changes to this bug.