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

Issue 661183 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Blocking:
issue 600740



Sign in to add a comment

Chromium archived build needs to include icudtl.dat

Project Member Reported by dmazz...@chromium.org, Nov 1 2016

Issue description

The archived builds used by the bisect script don't
include icudtl.dat, forcing the developer to grab
their own copy - this causes problems if they pick
the wrong version

Anyone know who owns the script that packages the
archived builds used for bisecting?

I think this is mainly an issue for Chromium builds
of Linux and Chrome OS. The official Chrome builds aren't
a problem since they package everything.

@glevin and I can provide more details if this is
unclear, I just don't know who owns the packaging
scripts or even where they live


 
Components: -Infra Infra>Client>Chrome
Cc: mmoss@chromium.org
Labels: -OS-Linux
Status: Available (was: Untriaged)
mmoss is this your team? Where are you getting the archived builds? What bisect script are you using?

Comment 3 by mmoss@chromium.org, Jan 27 2018

Cc: pras...@chromium.org
I'm not sure which builds are used for that, but I think most things that get archived, from wherever, are still defined by the FILES.cfg files:

https://chromium.googlesource.com/chromium/src.git/+/master/chrome/tools/build/win/FILES.cfg

+prasadv, who knows about bisect stuff, and can probably verify which archives we're talking about.

Comment 4 by mmoss@chromium.org, Jan 27 2018

Hrm, and it looks like icudtl.dat is defined in there:


https://chromium.googlesource.com/chromium/src.git/+/master/chrome/tools/build/win/FILES.cfg#101

so if it's not in the bisect archives, then I have no idea how those are being generated.

Comment 5 by glevin@chromium.org, Jan 27 2018

Note that blocked  Issue 600740  contains more info about how this affects bisects in practice. 

Comment 6 by prasadv@google.com, Jan 28 2018

Cc: dtu@chromium.org
Bisect uses lightweight builds of the binaries produced by chromeperf builders(https://uberchromegw.corp.google.com/i/chromium.perf/console). These builds are stored at https://pantheon.corp.google.com/storage/browser/chrome-test-builds/official-by-commit. 
Looks like icudtl.dat file is also included in the archive used for bisects.
https://logs.chromium.org/v/?s=chrome%2Fbb%2Fchromium.perf%2FLinux_Builder%2F176694%2F%2B%2Frecipes%2Fsteps%2Fpackage_build_for_bisect%2F0%2Fstdout.

+dtu@ from chromeperf team

Sign in to add a comment