Closed Bug 589616 Opened 14 years ago Closed 14 years ago

[SeaMonkey 2.1, mochitest-chrome] test_clear_button_disabled.xul | Test timed out.

Categories

(SeaMonkey :: Download & File Handling, defect)

Product:
SeaMonkey
Component:
Download & File Handling
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: kairo, Unassigned)

References

(Blocks 1 open bug,
URL
)

Details

(Keywords: intermittent-failure, Whiteboard: [sm-perma])

http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1282499502.1282502435.6363.gz 7306 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/suite/common/downloads/tests/test_clear_button_disabled.xul | Test timed out. Another failure in suite - those shouldn't happen. :(
Summary: [SeaMonkey 2.1, mochitest-browser-chrome] test_clear_button_disabled.xul | Test timed out. → [SeaMonkey 2.1, mochitest-chrome] test_clear_button_disabled.xul | Test timed out.
(In reply to comment #0) > http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1282499502.1282502435.6363.gz Linux comm-central-trunk debug test mochitest-other on 2010/08/22 10:51:42 *** [Mozilla/5.0 (Windows NT 5.0; rv:2.0b5pre) Gecko/20100825 SeaMonkey/2.1b1pre] (comm-central-trunk-win32/1282796695) Local execution: [Would seem to be 100% reproducible] 4 checks pass :-) D.M. window stays open :-/ test times out :-( *** At first history search, it would look like this was reported by Linux TinderBoxes only (...), and would have been fixed during http://tinderbox.mozilla.org/showbuilds.cgi?tree=SeaMonkey&maxdate=1282794372&hours=24&legend=0&norules=1 http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1282802323.1282805474.6625.gz Linux comm-central-trunk debug test mochitest-other on 2010/08/25 22:58:43 http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1282814300.1282816891.31159.gz Linux comm-central-trunk debug test mochitest-other on 2010/08/26 02:18:20 http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=f1b1e827d401&tochange=fe75089fbd26 out of which I see no obviously related bug :-/ *** Then, all this doesn't make much sense to me :-/ (perma vs non-perma, Linux vs others, ...) Hopefully, someone else can sort this bug out...
URL: http://mxr.mozilla.org/comm-central/f...
On 2.1 this might get fixed by my landing for bug 592438
Fwiw, this "non-perma-orange" just happened on SM 2.0: http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey2.0/1283292761.1283293821.5126.gz Linux comm-1.9.1 test mochitest-other on 2010/08/31 15:12:41
status-seamonkey2.1: --- → ?
Summary: [SeaMonkey 2.1, mochitest-chrome] test_clear_button_disabled.xul | Test timed out. → [SeaMonkey 2.0/2.1, mochitest-chrome] test_clear_button_disabled.xul | Test timed out.
The seamonkey2.1 flag is not for 2.0! Also, right now, we should focus on perma-failures on 2.1, then on intermittent ones on newer branches and then, when it's still alive, we can look at intermittent ones on 2.0 - at least IMHO (esp. as Firefox people mostly seem to ignore even perma-orange on FF 3.5 nowadays).
status-seamonkey2.1: ? → ---
serge, please don't morph bugs like this unnecessarily. And we want to concentrate on 2.1, if you _know_ the fix for a 2.0 orange, please do file a specific bug on that and patch it, but I'm not wanting to waste energy (including bug triage) on 2.0 at the moment.
Summary: [SeaMonkey 2.0/2.1, mochitest-chrome] test_clear_button_disabled.xul | Test timed out. → [SeaMonkey 2.1, mochitest-chrome] test_clear_button_disabled.xul | Test timed out.
Are we sure this is still happening on 2.1?
No its not, it also reports as: 14029 INFO TEST-KNOWN-FAIL | chrome://mochikit/content/chrome/toolkit/mozapps/downloads/tests/chrome/test_clear_button_disabled.xul | skip test for toolkit download manager UI So was a test issue too.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Whiteboard: [sm-perma][orange] → [sm-perma]
You need to log in before you can comment on or make changes to this bug.