1273426 - Intermittent marAppInUseStageFailureCompleteSvc_win.js,marCallbackAppStageSuccessCompleteSvc_win.js,marStageSuccessPartialSvc.js | timerCallback - [timerCallback : 2208] the update status should equal the expected value - "failed: 29" == "applied"

Status: RESOLVED DUPLICATE of bug 1291985

(Toolkit :: Application Update, defect)

Description

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

https://treeherder.mozilla.org/logviewer.html#?job_id=27995653&repo=mozilla-inbound

00:35:49     INFO -  TEST-START | toolkit/mozapps/update/tests/unit_service_updater/marAppInUseStageFailureCompleteSvc_win.js
00:38:51  WARNING -  TEST-UNEXPECTED-FAIL | toolkit/mozapps/update/tests/unit_service_updater/marAppInUseStageFailureCompleteSvc_win.js | xpcshell return code: 0
00:38:51     INFO -  TEST-INFO took 182219ms
...
00:38:52     INFO -  "00:35:55:607 | TEST-INFO | ../data/xpcshellUtilsAUS.js | [RUUS_TC_LC_FE : 2205] FINISH REMOVEFILE 3/3text0"
00:38:52     INFO -  "00:35:55:607 | TEST-INFO | ../data/xpcshellUtilsAUS.js | [RUUS_TC_LC_FE : 2205] succeeded"
00:38:52     INFO -  "00:35:55:608 | TEST-INFO | ../data/xpcshellUtilsAUS.js | [RUUS_TC_LC_FE : 2205] calling QuitProgressUI"
00:38:52     INFO -  "00:35:55:608 | TEST-INFO | ../data/xpcshellUtilsAUS.js | [RUUS_TC_LC_FE : 2205] "
00:38:52  WARNING -  TEST-UNEXPECTED-FAIL | toolkit/mozapps/update/tests/unit_service_updater/marAppInUseStageFailureCompleteSvc_win.js | timerCallback - [timerCallback : 2208] the update status should equal the expected value - "failed: 29" == "applied"

Comment 1

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

marCallbackAppStageSuccessCompleteSvc_win.js: https://treeherder.mozilla.org/logviewer.html#?job_id=28000807&repo=mozilla-inbound

Comment 3

[Robert Strong (they/them - no direct email)]

Attachment: failure.log

Note: 29 = SERVICE_STILL_APPLYING_ON_SUCCESS

Comment 4

[Robert Strong (they/them - no direct email)]

All but one of these happened on Win XP debug and these tests were disabled on Win XP debug so resolving duplicate. Logging has been turned on for these tests so if it does happen again hopefully there will be something more useful to figure this out.