Closed Bug 1093040 Opened 10 years ago Closed 10 years ago

Intermittent test_pointer-events-1a.xhtml | Test timed out. - expected PASS

Categories

(Core :: SVG, defect)

Product:
Core
Component:
SVG
Platform:
x86
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla36
Tracking Flags:
Tracking Status
firefox34 --- unaffected
firefox35 --- unaffected
firefox36 --- fixed
firefox-esr31 --- unaffected

People

(Reporter: cbook, Unassigned)

References

(
URL
)

Details

(Keywords: intermittent-failure)

b2g_emulator_vm mozilla-inbound debug test mochitest-debug-14 https://treeherder.mozilla.org/ui/logviewer.html#?job_id=3522984&repo=mozilla-inbound 02:19:57 INFO - 102 INFO TEST-UNEXPECTED-FAIL | /tests/dom/svg/test/test_pointer-events-1a.xhtml | Test timed out. - expected PASS
this seems fairly frequent, could this be related to Bug 946065 ?
Flags: needinfo?(birunthan)
(In reply to Carsten Book [:Tomcat] from comment #1) > this seems fairly frequent, could this be related to Bug 946065 ? Has this been happening since then? You only just opened this bug, but maybe we've not been staring this failure for a while?
(In reply to Jonathan Watt [:jwatt] from comment #8) > (In reply to Carsten Book [:Tomcat] from comment #1) > > this seems fairly frequent, could this be related to Bug 946065 ? > > Has this been happening since then? You only just opened this bug, but maybe > we've not been staring this failure for a while? retriggered the results for https://treeherder.mozilla.org/ui/#/jobs?repo=mozilla-inbound&revision=87f42360c1bd to see how intermittent this is
No, it started today. I've got some retriggers running and I intend to backout whatever caused it to spike.
(In reply to Carsten Book [:Tomcat] from comment #1) > this seems fairly frequent, could this be related to Bug 946065 ? Probably not based on comment 30.
Flags: needinfo?(birunthan)
Which basically means that this test is a timebomb for anything that changes the chunking around a bit. I vote disabling the test until that can be resolved.
How is this affecting/being affected by other tests around it? I presume any timeout is per test, not per group of tests?
Could be state pollution, GC timing changes, etc. However, I also just backed out a Nuwa patch (bug 1050122) for dramatically slowing down B2G debug mochitests on the whole, so let's see what affect that has here too.
Looks like the backout worked.
Blocks: 1050122
Status: NEW → RESOLVED
Closed: 10 years ago
status-firefox34: --- → unaffected
status-firefox35: --- → unaffected
status-firefox36: --- → fixed
status-firefox-esr31: --- → unaffected
Resolution: --- → FIXED
Target Milestone: --- → mozilla36
You need to log in before you can comment on or make changes to this bug.