Closed Bug 745756 Opened 12 years ago Closed 12 years ago

[SeaMonkey, Windows] Intermittent "test_resource_async.js | test failed (with xpcshell return code: -2147483645)", with "WARNING: NS_ENSURE_TRUE(mCacheEntry) failed"

Categories

(Firefox :: Sync, defect)

x86
Windows Server 2003
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: sgautherie, Unassigned)

References

(Blocks 1 open bug, )

Details

(Keywords: intermittent-failure)

SM 2.11:

http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1334581772.1334587140.25281.gz
WINNT 5.2 comm-central-trunk debug test xpcshell on 2012/04/16 06:09:32
s: cn-sea-qm-win2k3-01
{
TEST-UNEXPECTED-FAIL | e:\builds\slave\test\build\xpcshell\tests\services\sync\tests\unit\test_resource_async.js | test failed (with xpcshell return code: -2147483645), see following log:
[...]
TEST-INFO | (xpcshell/head.js) | exiting test
WARNING: NS_ENSURE_TRUE(mCacheEntry) failed: file e:/builds/slave/comm-cen-trunk-w32-dbg/build/mozilla/netwerk/protocol/http/nsHttpChannel.cpp, line 3115
WARNING: cannot post event if not initialized: file e:/builds/slave/comm-cen-trunk-w32-dbg/build/mozilla/netwerk/protocol/http/nsHttpConnectionMgr.cpp, line 211

TEST-PASS | (xpcshell/head.js) | 120 (+ 0) check(s) passed

TEST-INFO | (xpcshell/head.js) | 0 check(s) todo
JS Component Loader: ERROR e:/builds/slave/test/build/seamonkey/components/httpd.js:4170
                     TypeError: dumpn is not a function
WARNING: nsExceptionService ignoring thread destruction after shutdown: file e:/builds/slave/comm-cen-trunk-w32-dbg/build/mozilla/xpcom/base/nsExceptionService.cpp, line 199
+++ JavaScript debugging hooks removed.
###!!! ASSERTION: Component Manager being held past XPCOM shutdown.: 'cnt == 0', file e:/builds/slave/comm-cen-trunk-w32-dbg/build/mozilla/xpcom/build/nsXPComInit.cpp, line 723
[...]
PROCESS-CRASH | e:\builds\slave\test\build\xpcshell\tests\services\sync\tests\unit\test_resource_async.js | application crashed (minidump found)
}
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1333970687.1333976153.30040.gz
WINNT 5.2 comm-central-trunk debug test xpcshell on 2012/04/09 04:24:47
s: cb-seamonkey-win32-01

Same.
Summary: [cn-sea-qm-win2k3-01] Intermittent "test_resource_async.js | test failed (with xpcshell return code: -2147483645)" → [SeaMonkey, Windows] Intermittent "test_resource_async.js | test failed (with xpcshell return code: -2147483645)"
SM 2.10:

http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey-Aurora/1334547523.1334553576.30168.gz
WINNT 5.2 comm-aurora debug test xpcshell on 2012/04/15 20:38:43
s: cn-sea-qm-win2k3-01
Blocks: SmTestFail
Summary: [SeaMonkey, Windows] Intermittent "test_resource_async.js | test failed (with xpcshell return code: -2147483645)" → [SeaMonkey, Windows] Intermittent "test_resource_async.js | test failed (with xpcshell return code: -2147483645)", with "WARNING: NS_ENSURE_TRUE(mCacheEntry) failed"
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1335554483.1335560342.24344.gz&fulltext=1
WINNT 5.2 comm-central-trunk debug test xpcshell on 2012/04/27 12:21:23
s: cb-seamonkey-win32-02
(SM 2.10)
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey-Beta/1336029905.1336035992.27465.gz
WINNT 5.2 comm-beta debug test xpcshell on 2012/05/03 00:25:05
s: cn-sea-qm-win2k3-01
(In reply to TinderboxPushlog Robot from comment #5)
> anant
> https://tbpl.mozilla.org/php/getParsedLog.php?id=12324127&tree=Services-
> Central
> Rev3 WINNT 5.1 services-central debug test xpcshell on 2012-06-02 22:20:20
> slave: talos-r3-xp-037

(In reply to TinderboxPushlog Robot from comment #6)
> anant
> https://tbpl.mozilla.org/php/getParsedLog.php?id=13275848&tree=Services-
> Central
> Rev3 WINNT 6.1 services-central debug test xpcshell on 2012-07-05 20:21:05
> slave: talos-r3-w7-071

What makes you think this is the same bug?
I apologize, I should have marked them as bug 762606.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in before you can comment on or make changes to this bug.