Closed
Bug 758282
Opened 12 years ago
Closed 10 years ago
implement timeouts for testcases and make last running test visible
Categories
(Testing :: General, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: mah, Unassigned)
Details
<ochameau> hexmode: I don't know if it is easy/possible to implement. But for such testcase, it would be cool to handle timeout/python exception. And it would be just splendid if we can immediately see what was the last running test. [13:16] <ochameau> https://tbpl.mozilla.org/php/getParsedLog.php?id=11748127&tree=Mozilla-Aurora&full=1 <ochameau> in this test, the last running test was "info: executing 'test-collection.testAddRemove'" <ochameau> i.e. test-collection.testAddRemove <ochameau> or for this run: https://tbpl.mozilla.org/php/getParsedLog.php?id=12011115&tree=Firefox [13:17] <ochameau> firefox crashed during "info: executing 'test-tabs.test window focus changes active tab'"
Updated•12 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: [sheriff-want]
Updated•11 years ago
|
Keywords: sheriffing-untriaged
Whiteboard: [sheriff-want]
Comment 1•10 years ago
|
||
This needs to be handled at the harness level - and since this bug was filed, many more cases are handled correctly. I'll keep my eye out for any more and file specific bugs - please let me know if there are any specific cases that we don't handle currently :-)
No longer blocks: 778688
Status: NEW → RESOLVED
Closed: 10 years ago
Component: Tinderboxpushlog → General
Keywords: sheriffing-untriaged
Product: Webtools → Testing
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•