Closed Bug 1238838 Opened 9 years ago Closed 8 years ago

Intermittent e10s test_fullscreen-api.html | Test timed out

Categories

(Core :: DOM: Core & HTML, defect, P5)

Product:
Core
Component:
DOM: Core & HTML
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
e10s + ---
firefox46 --- affected

People

(Reporter: philor, Unassigned)

References

(Blocks 2 open bugs)

Details

(Keywords: intermittent-failure)

Blocks: e10s-tests
tracking-e10s: --- → +
Depends on: 1240696
I expect all linux-specific fullscreen intermittents could be fixed by bug 1254448...
Depends on: 1254448
No longer depends on: 1240696
No longer depends on: 1254448
Intermittent e10s test failure
Priority: -- → P5
The intermittent on OS X looks like a recent regression, and it also affects some other tests with fullscreen, like pointerlock test (bug 931445). Tomcat, could you help identifying what commit caused this regression? Or probably this is because of some infra change?
Flags: needinfo?(cbook)
(In reply to Xidorn Quan [:xidorn] (UTC+10) from comment #21) > The intermittent on OS X looks like a recent regression, and it also affects > some other tests with fullscreen, like pointerlock test (bug 931445). > > Tomcat, could you help identifying what commit caused this regression? Or > probably this is because of some infra change? hm i could trace the failure back to https://hg.mozilla.org/integration/mozilla-inbound/rev/73c6bdc7aa58f9139eb2d72377cffb56ad461f83 but not sure if this cause the problem. For infra changes #releng might be the best place to ask
Flags: needinfo?(cbook)
That doesn't seem to be something related. The problem is the failures on osx-10-10, which only starts appearing since last week as far as I can see. Or probably osx-10-10 was not counted by the robot before last week?
Flags: needinfo?(cbook)
That looks like a pretty reasonable result, then. Thanks! :)
Has this stopped again? It looks like bug 1292288 which has been fixed.
Flags: needinfo?(matt.woodrow)
Oh, okay. That's great, thanks!
I think this is now fixed given comment 27.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.