New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 601132 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Apr 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug

Blocked on:
issue 596885

Blocking:
issue 601134
issue 354261



Sign in to add a comment

mini_installer.exe doesn't work with GN (archive path is incorrect)

Project Member Reported by gab@chromium.org, Apr 6 2016

Issue description

Version: r385455
OS: Win10

What steps will reproduce the problem?
(1) Build mini_installer with GN (mine is component+branded but don't think it matters)
(2) Run mini_installer.exe --verbose-logging

Log:
(...)
[0406/143017:VERBOSE1:setup_util.cc(100)] Looking for Chrome version folder under C:\Users\Gabriel\AppData\Local\Google\Chrome\Temp\source2060_32606\Chrome-bin
[0406/143017:ERROR:setup_main.cc(1498)] Did not find any valid version in installer.
(...)

The same configuration build with GYP goes through the same steps but succeeds:
(...)
[0406/143052:VERBOSE1:setup_util.cc(100)] Looking for Chrome version folder under C:\Users\Gabriel\AppData\Local\Google\Chrome\Temp\source7532_17276\Chrome-bin
[0406/143052:VERBOSE1:setup_util.cc(111)] directory found: 51.0.2702.0
[0406/143052:VERBOSE1:setup_main.cc(1503)] version to install: 51.0.2702.0
(...)

Opening mini_installer.exe with 7-zip highlights the issue:
In the GN build the path is: mini_installer.exe\gen\temp_installer_archive\Chrome-bin\51.0.2702.0\
In the GYP build the path is: mini_installer.exe\Chrome-bin\51.0.2702.0\

The incorrect path is present in the chrome.7z generated by GN (i.e. that's likely the incorrect step).

Note: this is after  issue 596885  having been fixed.

 

Comment 1 by gab@chromium.org, Apr 6 2016

Blocking: 601134

Comment 2 by gab@chromium.org, Apr 12 2016

Cc: sshruthi@chromium.org brettw@chromium.org
Owner: dpranke@chromium.org
Status: Assigned (was: Untriaged)
Explicitly CC'ing people per Dirk's request on chromium-dev, this needs to be fixed before we shut off GYP on Windows for devs (assuming P1 + Windows + Proj-GN-Migration labels were sufficient but just making extra sure :-)).

Thanks,
Gab
Owner: ----
Status: Available (was: Assigned)
The labels are good enough :). Disclaiming ownership as I'm probably not going to work on this right away, so someone else is free to step up ...
Owner: brucedaw...@chromium.org
Status: Assigned (was: Available)
I just grabbed it.
Project Member

Comment 5 by bugdroid1@chromium.org, Apr 18 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/2d7f454406379fbf4e9221ff5328f4d364d754ca

commit 2d7f454406379fbf4e9221ff5328f4d364d754ca
Author: brucedawson <brucedawson@chromium.org>
Date: Mon Apr 18 17:27:54 2016

Fix mini_installer archive paths with gn

Due to a subtlety of 7za's behavior the file paths in the mini_installer
archive were incorrect in gn builds. This is a trivial change to make
them behave the same as in gyp builds.

BUG= 601132 

Review URL: https://codereview.chromium.org/1893823002

Cr-Commit-Position: refs/heads/master@{#387939}

[modify] https://crrev.com/2d7f454406379fbf4e9221ff5328f4d364d754ca/chrome/tools/build/win/create_installer_archive.py

Comment 6 by thakis@chromium.org, Apr 19 2016

done?
Status: Fixed (was: Assigned)
looks that way.

Sign in to add a comment