Closed Bug 588743 Opened 9 years ago Closed 7 years ago

test_popup_scaled.xul | anchored left position - got 98, expected 112, test_popup_scaled.xul | anchored top position - got 51, expected 58

Categories

(Toolkit :: XUL Widgets, defect)

x86_64
Linux
defect
Not set

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: masayuki, Unassigned)

References

Details

(Keywords: intermittent-failure)

masayuki%d-toybox.com
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1282215404.1282216004.13616.gz
Rev3 Fedora 12x64 mozilla-central opt test mochitests-5/5 on 2010/08/19
03:56:44

s: talos-r3-fed64-028
10565 ERROR TEST-UNEXPECTED-FAIL |
/tests/toolkit/content/tests/widgets/test_popup_scaled.xul | anchored left
position - got 98, expected 112
10566 ERROR TEST-UNEXPECTED-FAIL |
/tests/toolkit/content/tests/widgets/test_popup_scaled.xul | anchored top
position - got 51, expected 58
18327 ERROR TEST-UNEXPECTED-FAIL |
/tests/widget/tests/test_plugin_scroll_invalidation.html | Test timed out.

Similar to bug 585213, but the numbers and platform are different.
Blocks: 438871
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]
You need to log in before you can comment on or make changes to this bug.