Closed Bug 678691 Opened 12 years ago Closed 11 years ago

Intermittent test_native_mouse_mac.xul | Didn't receive expected event: {"type":"mouseover","target":"box","screenX":150,"screenY":170} | 2x received event I didn't expect

Categories

(Core :: Widget: Cocoa, defect)

Product:
Core
Component:
Widget: Cocoa
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure, regression) 

I badly misguessed the first instance (that I saw, who knows if it was really the first), thinking it looked like something in the way of focus, but there's a second one coming along (visible on buildbot but not yet on tinderbox), on 10.6 rather than 10.5 and thus also on another slave, and the way it gets them as unexpected after missing them as expected pretty much blows the blame-focus theory.

http://tinderbox.mozilla.org/showlog.cgi?log=Mozilla-Inbound/1313186367.1313187672.25485.gz
Rev3 MacOSX Leopard 10.5.8 mozilla-inbound opt test mochitest-other on 2011/08/12 14:59:27
s: talos-r3-leopard-022

32495 INFO TEST-PASS | chrome://mochitests/content/chrome/widget/tests/test_native_mouse_mac.xul | 22 | wrong target for event {"type":"click","target":"box","screenX":150,"screenY":170} - [object XULElement] should equal [object XULElement]
32496 INFO TEST-KNOWN-FAIL | chrome://mochitests/content/chrome/widget/tests/test_native_mouse_mac.xul | Didn't receive expected event: {"type":"mouseout","target":"box","screenX":150,"screenY":170}
32497 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/widget/tests/test_native_mouse_mac.xul | Didn't receive expected event: {"type":"mouseover","target":"box","screenX":150,"screenY":170}
32498 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/widget/tests/test_native_mouse_mac.xul | Didn't receive expected event: {"type":"mousemove","target":"box","screenX":150,"screenY":170}
32499 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/widget/tests/test_native_mouse_mac.xul | received event I didn't expect: {"type":"mouseover","target":"box","screenX":150,"screenY":170}
32500 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/widget/tests/test_native_mouse_mac.xul | received event I didn't expect: {"type":"mousemove","target":"box","screenX":150,"screenY":170}
32501 INFO TEST-PASS | chrome://mochitests/content/chrome/widget/tests/test_native_mouse_mac.xul | 23 | wrong X coord for event {"type":"mouseout","target":"box","screenX":200,"screenY":80} - 200 should equal 200

That one's on http://hg.mozilla.org/integration/mozilla-inbound/rev/fcb383e5e61e though it's apparently intermittent enough that the range is probably closer to a day.
Blocks: 675208
Keywords: regression
My patch in bug 716793 is likely to fix this.
Depends on: 716793