Closed Bug 753323 Opened 12 years ago Closed 12 years ago

Intermittent test_pointerlock-api.html | file_screenClientXYConst.html: screenY should be equal to where the mouse was originaly locked - got 266, expected 311

Categories

(Core :: DOM: Events, defect)

15 Branch
All
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: emorley, Unassigned)

References

Details

(Keywords: intermittent-failure)

+++ This bug was initially created as a clone of Bug #745009 +++

Rev3 Fedora 12 mozilla-inbound opt test mochitests-3/5 on 2012-05-09 07:12:58 PDT for push 47ab726a2a25

slave: talos-r3-fed-076

https://tbpl.mozilla.org/php/getParsedLog.php?id=11606070&tree=Mozilla-Inbound

{
[POINTERLOCK] Starting file_screenClientXYConst.html
13248 INFO TEST-PASS | /tests/dom/tests/mochitest/pointerlock/test_pointerlock-api.html | file_screenClientXYConst.html: Pointer should be unlocked
13249 INFO TEST-PASS | /tests/dom/tests/mochitest/pointerlock/test_pointerlock-api.html | file_screenClientXYConst.html: Pointer should be locked
13250 INFO TEST-PASS | /tests/dom/tests/mochitest/pointerlock/test_pointerlock-api.html | file_screenClientXYConst.html: clientX should be equal to where the mouse was originaly locked - 250 should equal 250
13251 INFO TEST-PASS | /tests/dom/tests/mochitest/pointerlock/test_pointerlock-api.html | file_screenClientXYConst.html: clientY should be equal to where the mouse was originaly locked - 266 should equal 266
13252 INFO TEST-PASS | /tests/dom/tests/mochitest/pointerlock/test_pointerlock-api.html | file_screenClientXYConst.html: screenX should be equal to where the mouse was originaly locked - 254 should equal 254
13253 ERROR TEST-UNEXPECTED-FAIL | /tests/dom/tests/mochitest/pointerlock/test_pointerlock-api.html | file_screenClientXYConst.html: screenY should be equal to where the mouse was originaly locked - got 266, expected 311
[POINTERLOCK] Finishing file_screenClientXYConst.html
}
https://hg.mozilla.org/integration/mozilla-inbound/rev/72a43b68ec95

I added the same work around to this test as I added to the mozMovementX pointer lock test (bug 745047) to stop it failing until I get bug 756334 fixed.
(In reply to Chris Pearce (:cpearce) from comment #60)
> https://hg.mozilla.org/integration/mozilla-inbound/rev/72a43b68ec95
> 
> I added the same work around to this test as I added to the mozMovementX
> pointer lock test (bug 745047) to stop it failing until I get bug 756334
> fixed.

https://hg.mozilla.org/mozilla-central/rev/72a43b68ec95
Hardware: x86 → All
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.