Closed Bug 971224 Opened 11 years ago Closed 6 years ago

Better log messages to troubleshoot failures of launching the service command

Categories

(Toolkit :: Application Update, defect)

x86
Windows 8.1
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: emk, Unassigned)

Details

No description provided.
FYI we already have a race between the elevated and unelevated updater. Here is first three lines from an update log (**** is my masked user name): > Performing a background update > calling QuitProgressUI > s\****\AppData\Local\Mozilla\updates\E7CF176E110C211B\updates\0 > DESTINATION DIRECTORY C:\Program Files (x86)\Mozilla Firefox\updated IIUC it should have been: > Performing a background update > SOURCE DIRECTORY C:\Users\****\AppData\Local\Mozilla\updates\E7CF176E110C211B\updates\0 > DESTINATION DIRECTORY C:\Program Files (x86)\Mozilla Firefox\updated But the unelevated updater has overwritten the log in WaitForServiceFinishThread. Am I correct?
Flags: needinfo?(robert.strong.bugs)
Yes. It would be good to fix that one that slipped through at the same time.
Flags: needinfo?(robert.strong.bugs)
Try run with the log patch: https://tbpl.mozilla.org/?tree=Try&rev=b02282d97cb5 An example of failed logs: https://tbpl.mozilla.org/php/getParsedLog.php?id=34534217&tree=Try&full=1 Indeed xpcshell tests fail, but "The post update process which runs as the user for service update could not be launched." is always displayed for succeeded non-staged updates. Is this failure expected?
Flags: needinfo?(robert.strong.bugs)
That isn't a failure for the tests. The tests don't launch the post update process intentionally.
Flags: needinfo?(robert.strong.bugs)

This was fixed awhile back so resolving as wfm

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.