Last modified: 2014-09-07 20:20:28 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 T68702, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 66702 - Add a tracking category if the running time exceeds a limit (lower than the execution time limit)
Add a tracking category if the running time exceeds a limit (lower than the e...
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Scribunto (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-06-17 08:42 UTC by Liangent
Modified: 2014-09-07 20:20 UTC (History)
3 users (show)

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


Attachments

Description Liangent 2014-06-17 08:42:25 UTC
Possibly due to some difference in system load at different time, script execution time of the same page may differ. If the running time is close to the limit, it still works fine most of the time, but fails with a "Script error" randomly.

When users report such a "Script error" or any consequence (eg. unexpanded template, missing *links etc.), it's difficult for us to diagnose until we get that "Script error" ourselves or have a look at the page source to find out that 9.x seconds execution time.

It would be great to give a warning (or put pages in a category) if the running time exceeds a soft limit, and kill execution only when it exceeds the hard limit.
Comment 1 Liangent 2014-06-17 08:44:51 UTC
I'm now suspecting this causes bug 60147.

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


Navigation
Links