Issue metadata
Sign in to add a comment
|
Regression: 56.0.2914.0 unable to Un-install. |
||||||||||||||||||||||
Issue descriptionVersion: 56.0.2914.0 OS: Windows-10 What steps will reproduce the problem? (1) Launch chrome and install signed/unsigned PGO build of 56.0.2914.0 (2) Try to uninstall and check. What is the expected result? > Should uninstall. What happens instead? > Unable to uninstall. Please use labels and text to provide additional information.
,
Nov 9 2016
taking a look now
,
Nov 9 2016
Able to reproduce the issue on windows 7 as well using chrome version 56.0.2914.0
,
Nov 9 2016
Regressed b/w previous canary(56.0.2913.0) and the latest(56.0.2914.0). Last good build: 56.0.2913.0 First bad build: 56.0.2914.0 Changelog: https://chromium.googlesource.com/chromium/src/+log/56.0.2913.0..56.0.2914.0?pretty=fuller&n=10000
,
Nov 9 2016
,
Nov 9 2016
Unable to repro. I just tried the unsigned win, win64, and win64-pgo with: mini_installer.exe --chrome-sxs --verbose-logging all three worked for me. Could you provide more info on how you are running the installer and the exact nature of the failure? Could you attach %TEMP%\chrome_installer.log?
,
Nov 9 2016
,
Nov 9 2016
,
Nov 9 2016
This is caused by my commit at r430728. I'll revert it and merge the revert to the branch.
,
Nov 9 2016
Reverted on trunk at r430914.
,
Nov 9 2016
Thanks for the quick turnaround and revert. Just to update, seeing one installer related top crash on Windows canary(56.0.2914.0) with magic signature:install_static::`anonymous namespace'::AppendChromeInstallSubDirectory as well and probably rooted to r430728. Link to the crashes: ==================== https://crash.corp.google.com/browse?q=custom_data.ChromeCrashProto.ptype%3D%27Chrome%20Installer%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27install_static%3A%3A%60anonymous%20namespace%5C%27%3A%3AAppendChromeInstallSubDirectory%27%20AND%20product.name%3D%27Chrome%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D
,
Nov 9 2016
Revert merged to 2914 at https://crrev.com/42f2553. Can anyone on the thread re-spin the Windows builds?
,
Nov 9 2016
Yes, that crash is the one.
,
Nov 9 2016
re-triggered Win builds on 2914 branch, will monitor and update the bug with details
,
Nov 9 2016
Marking as fixed since the offending change has been reverted on trunk and branch.
,
Nov 9 2016
It turns out that r430728 resulted in a test failure on the win_trunk continuous builder. I didn't get a nag email about the failure. If I had, I would have reverted this sooner. I'm enquiring with infra to find out why I didn't hear about the test failure.
,
Nov 9 2016
grt@, thank you for the revert. Latest trunk#56.0.2914.1 is working fine w/o any issues. Thank you Amit (ajha@) for finding this blocker issue. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ajha@chromium.org
, Nov 9 2016