Last modified: 2014-01-28 05:27:56 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 T22035, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 20035 - Parser test case data uploads don't send an abort in case of fatal
Parser test case data uploads don't send an abort in case of fatal
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
http://www.mediawiki.org/wiki/Special...
:
: 20282 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-08-02 07:45 UTC by Brion Vibber
Modified: 2014-01-28 05:27 UTC (History)
4 users (show)

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


Attachments

Description Brion Vibber 2009-08-02 07:45:21 UTC
Currently, when running parserTests.php --upload to send results to remote CodeReview server, we're only pinging a 'running' state at start, then 'complete' at end with the results.

If however a fatal PHP error causes the test suite run to cut off, currently the remote CodeReview repository will never see another ping and will leave the test run's state as "running".

A straightforward provision to ping the remote with an 'abort' would be nice... alternately adding support to CodeReview to time out a test run that's gone for an unusually long time should do it.
Comment 1 Chad H. 2009-08-16 20:06:39 UTC
*** Bug 20282 has been marked as a duplicate of this bug. ***
Comment 2 Bugmeister Bot 2011-08-19 19:12:25 UTC
Unassigning default assignments. http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/54734
Comment 3 db [inactive,noenotif] 2012-12-09 12:34:49 UTC
Invalid with gerrit/jenkins?
Comment 4 Quim Gil 2013-03-16 06:57:25 UTC
Looks live INVALID, yes.
Comment 5 Quim Gil 2014-01-28 05:27:56 UTC
Nobody complained, hence resolving as INVALID.

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


Navigation
Links