Closed
Bug 733188
Opened 12 years ago
Closed 12 years ago
Windows build signing intermittently wrong, causing 14 failures in test_0000_bootstrap_svc.js
Categories
(Release Engineering :: General, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: philor, Assigned: bhearsum)
References
Details
(Keywords: intermittent-failure)
e.g. https://tbpl.mozilla.org/php/getParsedLog.php?id=9832408&tree=Mozilla-Inbound Rev3 WINNT 5.1 mozilla-inbound opt test xpcshell on 2012-03-05 14:14:02 PST for push 8b8c280f4df0 TEST-UNEXPECTED-FAIL | c:\talos-slave\test\build\xpcshell\tests\toolkit\mozapps\update\test_svc\unit\test_0000_bootstrap_svc.js | test failed (with xpcshell return code: 0), see following log: TEST-UNEXPECTED-FAIL | c:/talos-slave/test/build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/head_update.js | failed: 26 == succeeded - See following stack: TEST-UNEXPECTED-FAIL | c:\talos-slave\test\build\xpcshell\tests\toolkit\mozapps\update\test_svc\unit\test_0110_general_svc.js | test failed (with xpcshell return code: 0), see following log: TEST-UNEXPECTED-FAIL | c:/talos-slave/test/build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/head_update.js | failed: 26 == succeeded - See following stack: TEST-UNEXPECTED-FAIL | c:\talos-slave\test\build\xpcshell\tests\toolkit\mozapps\update\test_svc\unit\test_0111_general_svc.js | test failed (with xpcshell return code: 0), see following log: TEST-UNEXPECTED-FAIL | c:/talos-slave/test/build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/head_update.js | failed: 26 == succeeded - See following stack: TEST-UNEXPECTED-FAIL | c:\talos-slave\test\build\xpcshell\tests\toolkit\mozapps\update\test_svc\unit\test_0112_general_svc.js | test failed (with xpcshell return code: 0), see following log: TEST-UNEXPECTED-FAIL | c:/talos-slave/test/build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/head_update.js | -1 != -1 - See following stack: TEST-UNEXPECTED-FAIL | c:\talos-slave\test\build\xpcshell\tests\toolkit\mozapps\update\test_svc\unit\test_0150_appBinReplaced_xp_win_complete_svc.js | test failed (with xpcshell return code: 0), see following log: TEST-UNEXPECTED-FAIL | c:/talos-slave/test/build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/head_update.js | failed: 26 == succeeded - See following stack: TEST-UNEXPECTED-FAIL | c:\talos-slave\test\build\xpcshell\tests\toolkit\mozapps\update\test_svc\unit\test_0151_appBinPatched_xp_win_partial_svc.js | test failed (with xpcshell return code: 0), see following log: TEST-UNEXPECTED-FAIL | c:/talos-slave/test/build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/head_update.js | failed: 26 == succeeded - See following stack: TEST-UNEXPECTED-FAIL | c:\talos-slave\test\build\xpcshell\tests\toolkit\mozapps\update\test_svc\unit\test_0160_appInUse_xp_win_complete_svc.js | test failed (with xpcshell return code: 0), see following log: TEST-UNEXPECTED-FAIL | c:/talos-slave/test/build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/head_update.js | failed: 26 == succeeded - See following stack: TEST-UNEXPECTED-FAIL | c:\talos-slave\test\build\xpcshell\tests\toolkit\mozapps\update\test_svc\unit\test_0170_fileLocked_xp_win_complete_svc.js | test failed (with xpcshell return code: 0), see following log: TEST-UNEXPECTED-FAIL | c:/talos-slave/test/build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/head_update.js | -1 != -1 - See following stack: TEST-UNEXPECTED-FAIL | c:\talos-slave\test\build\xpcshell\tests\toolkit\mozapps\update\test_svc\unit\test_0171_fileLocked_xp_win_partial_svc.js | test failed (with xpcshell return code: 0), see following log: TEST-UNEXPECTED-FAIL | c:/talos-slave/test/build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/head_update.js | -1 != -1 - See following stack: TEST-UNEXPECTED-FAIL | c:\talos-slave\test\build\xpcshell\tests\toolkit\mozapps\update\test_svc\unit\test_0180_fileInUse_xp_win_complete_svc.js | test failed (with xpcshell return code: 0), see following log: TEST-UNEXPECTED-FAIL | c:/talos-slave/test/build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/head_update.js | failed: 26 == succeeded - See following stack: TEST-UNEXPECTED-FAIL | c:\talos-slave\test\build\xpcshell\tests\toolkit\mozapps\update\test_svc\unit\test_0181_fileInUse_xp_win_partial_svc.js | test failed (with xpcshell return code: 0), see following log: TEST-UNEXPECTED-FAIL | c:/talos-slave/test/build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/head_update.js | failed: 26 == succeeded - See following stack: TEST-UNEXPECTED-FAIL | c:\talos-slave\test\build\xpcshell\tests\toolkit\mozapps\update\test_svc\unit\test_0182_rmrfdirFileInUse_xp_win_complete_svc.js | test failed (with xpcshell return code: 0), see following log: TEST-UNEXPECTED-FAIL | c:/talos-slave/test/build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/head_update.js | failed: 26 == succeeded - See following stack: TEST-UNEXPECTED-FAIL | c:\talos-slave\test\build\xpcshell\tests\toolkit\mozapps\update\test_svc\unit\test_0183_rmrfdirFileInUse_xp_win_partial_svc.js | test failed (with xpcshell return code: 0), see following log: TEST-UNEXPECTED-FAIL | c:/talos-slave/test/build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/head_update.js | failed: 26 == succeeded - See following stack: TEST-UNEXPECTED-FAIL | c:\talos-slave\test\build\xpcshell\tests\toolkit\mozapps\update\test_svc\unit\test_0200_app_launch_apply_update_svc.js | test failed (with xpcshell return code: 0), see following log: TEST-UNEXPECTED-FAIL | c:/talos-slave/test/build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/head_update.js | failed: 26 == succeeded - See following stack: <bbondy>: philor bhearsum|buildduty the binaries for the build philor linked me to is signed by "My Company Ltd". Should be the Nightly cert though. <bbondy>: Issuer Mozilla Fake CA <bbondy>: so 16002 is expected in that case (16002 being what I hope is just a different flavor of the same error, where instead of "26 == succeeded" it's "16002 == succeeded")
Comment 1•12 years ago
|
||
This push to inbound: https://tbpl.mozilla.org/?tree=Mozilla-Inbound&rev=980483ace374 And in particular this change: https://hg.mozilla.org/integration/mozilla-inbound/rev/7a690d2c2e23 Changes code 16002 to 26 to fix an existing updater telemetry problem. So both are the same error and both re because the builds are being signed as "My Company Ltd".
Updated•12 years ago
|
Priority: -- → P1
Comment hidden (Legacy TBPL/Treeherder Robot) |
Comment 3•12 years ago
|
||
I put this as a P1 because if this problem ever happened on a Nightly build it could lock people out of updates.
Comment hidden (Legacy TBPL/Treeherder Robot) |
Comment hidden (Legacy TBPL/Treeherder Robot) |
Comment 6•12 years ago
|
||
I thought we didn't use the nightly cert on non-nightly builds, like the two given so far (inbound dep).
Comment 7•12 years ago
|
||
I think I should have used the name level 3 repo cert.
Comment 8•12 years ago
|
||
This is related to authenticode binary signing by the way not MAR signing.
Comment hidden (Legacy TBPL/Treeherder Robot) |
Comment hidden (Legacy TBPL/Treeherder Robot) |
Comment hidden (Legacy TBPL/Treeherder Robot) |
Comment hidden (Legacy TBPL/Treeherder Robot) |
Comment hidden (Legacy TBPL/Treeherder Robot) |
Comment hidden (Legacy TBPL/Treeherder Robot) |
Comment hidden (Legacy TBPL/Treeherder Robot) |
Comment hidden (Legacy TBPL/Treeherder Robot) |
Reporter | ||
Comment 17•12 years ago
|
||
https://tbpl.mozilla.org/php/getParsedLog.php?id=9841897&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=9841950&tree=Mozilla-Inbound Must be client cache. Must be.
Reporter | ||
Comment 18•12 years ago
|
||
https://tbpl.mozilla.org/php/getParsedLog.php?id=9842395&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=9842404&tree=Mozilla-Inbound Cache. Cache. Such a soft pleasant reassuring word.
Reporter | ||
Comment 19•12 years ago
|
||
https://tbpl.mozilla.org/php/getParsedLog.php?id=9844312&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=9844332&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=9844146&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=9844205&tree=Mozilla-Inbound Cache. Such an increasingly unlikely explanation as time goes on :(
Comment hidden (Legacy TBPL/Treeherder Robot) |
Comment hidden (Legacy TBPL/Treeherder Robot) |
Assignee | ||
Comment 22•12 years ago
|
||
The last failure I see is on https://tbpl.mozilla.org/?tree=Mozilla-Inbound&rev=2c215049a637. I tracked down its build log and indeed it had files cached on the client side. I've just set a clobber for the opt and debug windows builds on Inbound, which will flush that cache. This problem *is* fixed now, though.
Assignee: nobody → bhearsum
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 23•12 years ago
|
||
Ftr, it looks like bug 718922 comment 13(+) happened after comment 22...
Comment 24•12 years ago
|
||
Has mozilla-central been clobbered? https://tbpl.mozilla.org/php/getParsedLog.php?id=9856152&tree=Firefox
Assignee | ||
Comment 25•12 years ago
|
||
No, I only clobbered m-i.
Comment 26•12 years ago
|
||
I'll clobber m-c right now, then.
Updated•12 years ago
|
Keywords: intermittent-failure
Updated•12 years ago
|
Whiteboard: [orange]
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•