Closed Bug 539332 Opened 15 years ago Closed 15 years ago

Tinderbox orange: "chrome://mochikit/content/chrome/widget/tests/test_native_mouse_mac.xul | didn't receive expected event: ..."

Categories

(Release Engineering :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: cjones, Unassigned)

References

Details

(Keywords: intermittent-failure)

OS X 10.5.2 mozilla-central opt test everythingelse on 2010/01/12 13:13:59 http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1263330839.1263334019.30848.gz s: bm-xserve19 8194 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/widget/tests/test_native_mouse_mac.xul | didn't receive expected event: {"type":"mouseover","target":"window","screenX":400,"screenY":180} 8208 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/widget/tests/test_native_mouse_mac.xul | didn't receive expected event: {"type":"mousemove","target":"window","screenX":410,"screenY":180} 8209 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/widget/tests/test_native_mouse_mac.xul | didn't receive expected event: {"type":"mousemove","target":"window","screenX":411,"screenY":180} 8210 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/widget/tests/test_native_mouse_mac.xul | didn't receive expected event: {"type":"mousemove","target":"window","screenX":412,"screenY":180} 8213 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/widget/tests/test_native_mouse_mac.xul | 38 | wrong event type for event {"type":"mouseover","target":"window","screenX":412,"screenY":80} - got "mouseover", expected "mousemove" 8215 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/widget/tests/test_native_mouse_mac.xul | received event I didn't expect: {"type":"mousemove","target":"window","screenX":412,"screenY":80} 8230 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/widget/tests/test_native_mouse_mac.xul | 42 | wrong event type for event {"type":"mouseout","target":"window","screenX":390,"screenY":170} - got "mouseout", expected "mousemove" 8232 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/widget/tests/test_native_mouse_mac.xul | didn't receive expected event: {"type":"mousemove","target":"window","screenX":390,"screenY":171} 8233 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/widget/tests/test_native_mouse_mac.xul | didn't receive expected event: {"type":"mousemove","target":"window","screenX":391,"screenY":171} 8234 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/widget/tests/test_native_mouse_mac.xul | didn't receive expected event: {"type":"mouseout","target":"window","screenX":260,"screenY":170} 8239 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/widget/tests/test_native_mouse_mac.xul | didn't receive expected event: {"type":"mouseover","target":"panel","screenX":387,"screenY":170} 8240 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/widget/tests/test_native_mouse_mac.xul | didn't receive expected event: {"type":"mousemove","target":"panel","screenX":387,"screenY":170} 8241 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/widget/tests/test_native_mouse_mac.xul | didn't receive expected event: {"type":"mousemove","target":"panel","screenX":387,"screenY":171} 8242 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/widget/tests/test_native_mouse_mac.xul | didn't receive expected event: {"type":"mousemove","target":"panel","screenX":388,"screenY":171} 8257 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/widget/tests/test_native_mouse_mac.xul | 47 | wrong event type for event {"type":"mouseover","target":"box","screenX":173,"screenY":200} - got "mouseover", expected "mouseout" 8258 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/widget/tests/test_native_mouse_mac.xul | 47 | wrong target for event {"type":"mouseover","target":"box","screenX":173,"screenY":200} - got [object XULElement], expected [object XULElement] 8261 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/widget/tests/test_native_mouse_mac.xul | 48 | wrong event type for event {"type":"mousemove","target":"box","screenX":173,"screenY":200} - got "mousemove", expected "mouseover" 8263 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/widget/tests/test_native_mouse_mac.xul | didn't receive expected event: {"type":"mousemove","target":"box","screenX":173,"screenY":200}
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1263373754.1263375535.30885.gz OS X 10.5.2 mozilla-central test everythingelse on 2010/01/13 01:09:14 s: bm-xserve19
Blocks: 438871
Whiteboard: [orange]
Version: unspecified → Trunk
2 failures within 12 hours --> this probably regressed during the last day or two. Looking at the pushlog for that range, Bug 539020 and Bug 526394 are the only checkins whose messages stand out to me as suspicious (mouse-event-related). Of those, Bug 539020 is a one-liner in plugin-only code, so I don't think it could cause this. That leaves Bug 526394 as the likely regressor. I'm tentatively marking this as blocking that bug.
Blocks: 526394
Assignee: nobody → mstange
Status: NEW → ASSIGNED
I think this is a machine issue since both failures were on bm-xserve19. The failures point to some left-over, always-on-top window that blocks mouse move events that occur near the pixel (395, 175).
Assignee: mstange → nobody
Status: ASSIGNED → NEW
Component: DOM: Events → Release Engineering
Product: Core → mozilla.org
QA Contact: events → release
Version: Trunk → other
No longer blocks: 526394
So this box has a "The computer was restarted after Mac OS X quit unexpectedly" dialog up. I've dismissed it, let's see if this error comes back. Any ideas how to get rid of this dialog automatically?
Thanks! I have no idea how to do this automatically, sorry.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Wow, that dialog persists over reboots ?
This was a machine issue in the past, and it just cropped up again: http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1266449338.1266450273.6126.gz&fulltext=1
Cleared the prompt (same as comment #4) on bm-xserve18.
Whiteboard: [orange]
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.