Closed Bug 569299 Opened 14 years ago Closed 12 years ago

Intermittent "automation.py | application timed out after 330 seconds with no output" timeout after browser_signed_multiple.js | must wait for focus

Categories

(Toolkit :: Add-ons Manager, defect)

Product:
Toolkit
Component:
Add-ons Manager
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure) 

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1275358020.1275359449.17439.gz
Rev3 Fedora 12x64 mozilla-central opt test mochitest-other on 2010/05/31 19:07:00
s: talos-r3-fed64-014

TEST-PASS | chrome://mochikit/content/browser/toolkit/mozapps/extensions/test/xpinstall/browser_signed_multiple.js | must wait for focus
TEST-UNEXPECTED-FAIL | automation.py | application timed out after 330 seconds with no output
Comment 1 is actually bug 562803, a different timeout from a different source in a different part of the test with different results (this one kills the rest of the suite).
Summary: Intermittent timeout after browser_signed_multiple.js | must wait for focus → Intermittent "automation.py | application timed out after 330 seconds with no output" timeout after browser_signed_multiple.js | must wait for focus
Depends on: 543278
Seems to have gone away so there is no reason to keep this open.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Seems to have started happening again.
Status: RESOLVED → REOPENED
OS: Linux → All
Resolution: WORKSFORME → ---
Mass marking whiteboard:[orange] bugs WFM (to clean up TBPL bug suggestions) that:
* Haven't changed in > 6months
* Whose whiteboard contains none of the strings: {disabled,marked,random,fuzzy,todo,fails,failing,annotated,leave open,time-bomb}
* Passed a (quick) manual inspection of bug summary/whiteboard to ensure they weren't a false positive.

I've also gone through and searched for cases where the whiteboard wasn't labelled correctly after test disabling, by using attachment description & basic comment searches. However if the test for which this bug was about has in fact been disabled/annotated/..., please accept my apologies & reopen/mark the whiteboard appropriately so this doesn't get re-closed in the future (and please ping me via IRC or email so I can try to tweak the saved searches to avoid more edge cases).

Sorry for the spam! Filter on: #FFA500
Status: REOPENED → RESOLVED
Closed: 14 years ago → 12 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.