Closed Bug 607727 Opened 14 years ago Closed 12 years ago

Intermittent failure in browser_bug577990.js | Should have correct hidden/selected state - Got true, expected false and browser_bug577990.js | Should have correct selected state - Got true, expected false

Categories

(Toolkit :: Add-ons Manager, defect)

x86
Windows Server 2003
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure)

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1288205072.1288208855.4918.gz
WINNT 5.2 mozilla-central debug test mochitest-other on 2010/10/27 11:44:32
s: win32-slave26

TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser-window/browser_bug577990.js | Should have correct hidden state - Got true, expected false
TEST-PASS | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser-window/browser_bug577990.js | Should have an add-ons manager window
TEST-PASS | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser-window/browser_bug577990.js | Should be displaying the correct UI
TEST-INFO | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser-window/browser_bug577990.js | Waiting for initialization
WARNING: Failed to create Device for DeviceManagerD3D9.: file e:/builds/moz2_slave/mozilla-central-win32-debug/build/gfx/layers/d3d9/DeviceManagerD3D9.cpp, line 325
TEST-INFO | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser-window/browser_bug577990.js | Console message: CoCreateInstance() FAILED.

TEST-PASS | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser-window/browser_bug577990.js | Should not get category when manager window is not loaded
TEST-PASS | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser-window/browser_bug577990.js | Should not check visible state when manager window is not loaded
TEST-PASS | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser-window/browser_bug577990.js | Should have correct hidden state
TEST-PASS | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser-window/browser_bug577990.js | Should not get selected category when manager window is not loaded
TEST-PASS | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser-window/browser_bug577990.js | A category should be selected
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser-window/browser_bug577990.js | Should have correct selected state - Got true, expected false
TEST-INFO | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser-window/browser_bug577990.js | Test 8 took 1591ms
Taking
Assignee: nobody → robert.bugzilla
walking away from this bug for now
Assignee: robert.bugzilla → nobody
Summary: Intermittent failure in browser_bug577990.js | Should have correct hidden state - Got true, expected false and browser_bug577990.js | Should have correct hidden state - Got true, expected false → Intermittent failure in browser_bug577990.js | Should have correct hidden state - Got true, expected false and browser_bug577990.js | Should have correct selected state - Got true, expected false
Summary: Intermittent failure in browser_bug577990.js | Should have correct hidden state - Got true, expected false and browser_bug577990.js | Should have correct selected state - Got true, expected false → Intermittent failure in browser_bug577990.js | Should have correct hidden/selected state - Got true, expected false and browser_bug577990.js | Should have correct selected state - Got true, expected false
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: 12 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.