Probably just another bug 557406, etc., but: http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1270767313.1270769876.4610.gz WINNT 5.2 mozilla-central debug test xpcshell on 2010/04/08 15:55:13 s: win32-slave32 TEST-UNEXPECTED-FAIL | e:\builds\moz2_slave\mozilla-central-win32-debug-unittest-xpcshell\build\xpcshell\tests\test_places\unit\test_null_interfaces.js | test failed (with xpcshell return code: 0), see following log: TEST-UNEXPECTED-FAIL | e:/builds/moz2_slave/mozilla-central-win32-debug-unittest-xpcshell/build/xpcshell/tests/test_places/unit/test_null_interfaces.js | false == true - See following stack:
the test is catching unexpected exceptions from createFolder, exactly from the transaction.commit() call... I'm starting thinking our transactions management in Storage has some flaw when concurrent sync and async transactions exist.
i filed Bug 559678 and bug 559682 to try clarifying what happens, we still don't have a clear idea of how we could get NS_ERROR_FAILURE out of transaction.commit() without trying to commit a not existing transaction (since we use the Storage helper we don't even try to create a transaction if one already exists).
Whiteboard: [orange] → [orange][transaction.commit() failure]
Resolving Places oranges that don't appear on central from at least 6 months. Check dependencies for bugs that could have fixed the issue. Please reopen if they re-appear in central.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Whiteboard: [orange][transaction.commit() failure] → [transaction.commit() failure]
You need to log in before you can comment on or make changes to this bug.