Closed Bug 566936 Opened 15 years ago Closed 14 years ago

Intermittent timeout after browser_unsigned_url.js | must wait for focus

Categories

(Toolkit :: Add-ons Manager, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure)

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1274296094.1274297795.13408.gz Rev3 Fedora 12x64 mozilla-central debug test mochitest-other on 2010/05/19 12:08:14 s: talos-r3-fed64-031 TEST-INFO | checking window state TEST-PASS | chrome://mochikit/content/browser/toolkit/mozapps/extensions/test/xpinstall/browser_unsigned_url.js | before wait for focus -- loaded: complete active window: <no window active> focused window: <no window focused> desired window: ([object ChromeWindow @ 0x1850780 (native @ 0x1ebe940)]) chrome://browser/content/browser.xul child window: ([object XPCNativeWrapper [object Window @ 0x5041ff0 (native @ 0x3a30cc0)]]) about:blank docshell visible: true TEST-PASS | chrome://mochikit/content/browser/toolkit/mozapps/extensions/test/xpinstall/browser_unsigned_url.js | must wait for focus (bunch of GC) ###!!! ASSERTION: bad hint in chrome code: 'hint != XOW && hint != SOW && hint != COW', file /builds/slave/mozilla-central-linux64-debug/build/js/src/xpconnect/src/xpcwrappednativescope.cpp, line 1043 (several more times) TEST-UNEXPECTED-FAIL | automation.py | application timed out after 330 seconds with no output
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1274464569.1274466310.31939.gz Rev3 Fedora 12x64 mozilla-central debug test mochitest-other on 2010/05/21 10:56:09 s: talos-r3-fed64-014
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1275425941.1275428066.2549.gz Rev3 Fedora 12 mozilla-central debug test mochitest-other on 2010/06/01 13:59:01 s: talos-r3-fed-034
Depends on: 543278
Seems to have gone away so there is no reason to keep this open.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.