New issue
Advanced search Search tips

Issue 755168 link

Starred by 2 users
Status: Fixed
Owner: ----
Closed: Dec 13
Cc:
jbudorick@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Failed build attempts could provide detailed build instructions to users

Project Member Reported by cjgrant@chromium.org, Aug 14 2017 
ToT as of August 2017.

Failed dry-runs are part of life.  Many times, my change works on the targets I'm working with, but fails on a different platform or target (due to build, failed tests, etc).

It would be awesome if the builder output (as pointed to by the Gerrit UI) presented steps for a developer to easily recreate the build.  This could be as simple as the gn command (with args) needed to configure the build, and target to build.

Maybe the information *is* actually already presented, but not in a way that's obvious.

Comment 1 by cjgrant@chromium.org, Aug 14 2017 

Here is the snippet from our team's getting-started document.  This is how we overcome the problem currently:

--------

Courtesy of hanxi@, here’s some advice on how to get the gn build args from a trybot:
./tools/mb/mb.py gen -m chromium.linux -b "Android Builder" <output directory>
ninja -C <output directory> [options] <build target>
“chromium.linux” and “Android Builder” can be found in https://cs.chromium.org/chromium/src/tools/mb/mb_config.pyl
You need to find the bot info and replace "chromium.linux" and "Android Builder" in the first line

Example:
./tools/mb/mb.py gen -m tryserver.chromium.android -b android_arm64_dbg_recipe  out/android-no-vr/

Comment 2 by tandrii@chromium.org, Aug 15 2017

Components: -Infra>Platform>Buildbot Infra>Client>Chrome

Comment 3 by efoo@chromium.org, Sep 18 2017

Cc: jbudorick@chromium.org
Status: Available (was: Untriaged)
Project Member

Comment 4 by sheriffbot@chromium.org, Sep 19

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by jbudorick@chromium.org, Sep 19

Labels: -Pri-2 Pri-3
Status: Available (was: Untriaged)

Comment 6 by cjgrant@chromium.org, Dec 13

Status: Fixed (was: Available)
Between the time this issue was filed and now, GN args were added to the top-level steps of a build.  Very convenient.

Per discussion by VC, there is more that could be done to ease reproducing build failures, but that should be discussed separately, and we can file bugs if that work's ever deemed worthwhile.
►

Sign in to add a comment