Intermittent failure in content/events/test/test_bug602962.xul | Width should be resized - got 200, expected 600

RESOLVED WORKSFORME

Status

()

defect
RESOLVED WORKSFORME
8 years ago
7 years ago

People

(Reporter: Ehsan, Unassigned)

Tracking

({intermittent-failure})

Trunk
x86
macOS
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 years ago
http://tinderbox.mozilla.org/showlog.cgi?log=Mozilla-Inbound/1309168408.1309170496.28710.gz
Rev3 Fedora 12x64 mozilla-inbound opt test mochitest-other on 2011/06/27 02:53:28

1462 INFO TEST-START | chrome://mochitests/content/chrome/content/events/test/test_bug602962.xul
1463 INFO TEST-PASS | chrome://mochitests/content/chrome/content/events/test/test_bug602962.xul | Scroll X should not have changed yet - 200 should equal 200
1464 INFO TEST-PASS | chrome://mochitests/content/chrome/content/events/test/test_bug602962.xul | Scroll Y should not have changed yet - 0 should equal 0
1465 INFO TEST-PASS | chrome://mochitests/content/chrome/content/events/test/test_bug602962.xul | The MozBeforeResize event should already have fired - true should equal true
1466 INFO TEST-PASS | chrome://mochitests/content/chrome/content/events/test/test_bug602962.xul | Scroll X should have been restored to the value before the resize - 200 should equal 200
1467 INFO TEST-PASS | chrome://mochitests/content/chrome/content/events/test/test_bug602962.xul | Scroll Y should have been restored to the value before the resize - 0 should equal 0
1468 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/content/events/test/test_bug602962.xul | Width should be resized - got 200, expected 600
1469 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/content/events/test/test_bug602962.xul | Height should be resized - got 400, expected 601
1470 INFO TEST-END | chrome://mochitests/content/chrome/content/events/test/test_bug602962.xul | finished in 166ms
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
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.