Open Bug 1400586 Opened 9 years ago Updated 3 years ago

Intermittent dom/events/test/test_bug607464.html | Test timed out.

Categories

(Core :: DOM: Events, defect, P3)

defect

Tracking

()

Tracking Status
firefox57 --- disabled
firefox58 --- disabled

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: intermittent-failure, leave-open, Whiteboard: [stockwell unknown])

Here's another seemingly Stylo-related intermittent failure that, AFAICT, is failing on Linux with a test that was written for a macOS-specific fix (bug 607464) ... Jet?
Flags: needinfo?(bugs)
Priority: -- → P3
(In reply to Andrew Overholt [:overholt] from comment #3) > Here's another seemingly Stylo-related intermittent failure that, AFAICT, is > failing on Linux with a test that was written for a macOS-specific fix (bug > 607464) ... Jet? I'm seeing failures on the stylo-disabled variants as well. I don't think it's Stylo-related.
Flags: needinfo?(bugs)
This is basically intermittently green on Linux on Beta. NI myself to skip the test there at least.
Flags: needinfo?(ryanvm)
Priority: -- → P2
BTW, this skipped is already being skipped on OSX and Windows due to bug 1252273. Looks like it's time to give this test some TLC.
Flags: needinfo?(ryanvm)
Pushed by ryanvm@gmail.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/e922dceed924 Skip dom/events/test/test_bug607464.html on e10s runs across all platforms.
Priority: -- → P3
The leave-open keyword is there and there is no activity for 6 months. :hsinyi, maybe it's time to close this bug?
Flags: needinfo?(htsai)

This bug is still valid for re-enabling the test.

Flags: needinfo?(htsai)

Still fails frequently on Windows (~25% of the time) and less so on OSX (~5%). Looks OK on Linux.

(In reply to Ryan VanderMeulen [:RyanVM] from comment #19)

Still fails frequently on Windows (~25% of the time) and less so on OSX
(~5%). Looks OK on Linux.

I take that back, Linux is also in bad shape. Try fuzzy wasn't scheduling the right jobs :\

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.