Closed Bug 696453 Opened 8 years ago Closed 7 years ago

rev4 OS X 10.6/10.7 intermittent test_plugin_mouse_coords.html | p2 mouse down X - got -1, expected 15 and five more

Categories

(Release Engineering :: General, defect, P3)

x86_64
macOS
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure)

Another for which intermittently-wrong resolution seems as reasonable a bet as any other.

https://tbpl.mozilla.org/php/getParsedLog.php?id=6971168&tree=Firefox&full=1
Rev4 MacOSX Snow Leopard 10.6 mozilla-central debug test mochitests-4/5 on 2011-10-21 10:13:03 PDT for push 75eaad17724f

slave: talos-r4-snow-050

3495 ERROR TEST-UNEXPECTED-FAIL | /tests/layout/generic/test/test_plugin_mouse_coords.html | p2 mouse down X - got -1, expected 15
3496 ERROR TEST-UNEXPECTED-FAIL | /tests/layout/generic/test/test_plugin_mouse_coords.html | p2 mouse down Y - got -1, expected 18
3497 ERROR TEST-UNEXPECTED-FAIL | /tests/layout/generic/test/test_plugin_mouse_coords.html | p2 mouse move X - got -1, expected 15
3498 ERROR TEST-UNEXPECTED-FAIL | /tests/layout/generic/test/test_plugin_mouse_coords.html | p2 mouse move Y - got -1, expected 38
3499 ERROR TEST-UNEXPECTED-FAIL | /tests/layout/generic/test/test_plugin_mouse_coords.html | p2 mouse up X - got -1, expected 15
3500 ERROR TEST-UNEXPECTED-FAIL | /tests/layout/generic/test/test_plugin_mouse_coords.html | p2 mouse up Y - got -1, expected 28
No longer blocks: 683734
Depends on: r4-dongles
See Also: → 683734
Summary: rev4 OS X 10.6 intermittent test_plugin_mouse_coords.html | p2 mouse down X - got -1, expected 15 and five more → rev4 OS X 10.6/10.7 intermittent test_plugin_mouse_coords.html | p2 mouse down X - got -1, expected 15 and five more
^ talos-r4-lion-064 at 800x600x32
^ talos-r4-snow-048 at 800x600
^ talos-r4-lion-037 at 800x600
The fix for this bug is tracked in bug 720006
Depends on: 720006
No longer depends on: r4-dongles
Mass marking whiteboard:[orange] bugs WFM (to clean up TBPL bug suggestions) that:
* Haven't changed in > 6months
* Whose whiteboard contains none of the strings: {disabled,marked,random,fuzzy,todo,fails,failing,annotated,leave open,time-bomb}
* Passed a (quick) manual inspection of bug summary/whiteboard to ensure they weren't a false positive.

I've also gone through and searched for cases where the whiteboard wasn't labelled correctly after test disabling, by using attachment description & basic comment searches. However if the test for which this bug was about has in fact been disabled/annotated/..., please accept my apologies & reopen/mark the whiteboard appropriately so this doesn't get re-closed in the future (and please ping me via IRC or email so I can try to tweak the saved searches to avoid more edge cases).

Sorry for the spam! Filter on: #FFA500
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.