New issue
Advanced search Search tips

Issue 767524 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature



Sign in to add a comment

make it easier to find the builder link for nightly performance builders

Project Member Reported by llozano@chromium.org, Sep 21 2017

Issue description

currently, the sheriff gets a message like the following from the nightly performance builders

OB: Nightly test, squawks, llvm-next
Thu Sep 21 01:45:01 PDT 2017: starting 'buildbot_nightly_wrapper.sh squawks chromeos2-row9-rack10-host7.cros chromeos2-row9-rack10-host9.cros 513590,671853,671473,*457115'
Job failed with exit code 1
Completed performance run: check /usr/local/google/crostc/buildbot_tester.squawks.513590,671853,671473,*457115.Thu.out
Thu Sep 21 03:55:20 PDT 2017: done 'buildbot_nightly_wrapper.sh squawks chromeos2-row9-rack10-host7.cros chromeos2-row9-rack10-host9.cros 513590,671853,671473,*457115'


It is pretty annoying to have to go to chrotomation2 to look at the content of that log and find the link to the builder. 

The content of the log is like this: 

CMD (None): cros tryjob --yes --nochromesdk --remote-description master_513590_671853_671473_*457115_squawks-release_2017-09-21 --notests --latest-toolchain  -g '513590' -g '671853' -g '>
^[[1;33m01:45:16: WARNING: Patch yunlian:671853:074d01a7 has already been merged.^[[0m
ERROR: Trybot job master_513590_671853_671473_*457115_squawks-release_2017-09-21 failed with status 2; no trybot image generated.
Verifying patches...
Submitting tryjob...
Successfully sent PUT request to [buildbucket_bucket:master.chromiumos.tryserver] with [config:squawks-release] [buildbucket_id:8967855543310066176].
Tryjob submitted!
Go to https://uberchromegw.corp.google.com/i/chromiumos.tryserver/waterfall?committer=mobiletc-prebuild@google.com&builder=release to view the status of your job.
OUTPUT: trybot_image is ''
OUTPUT: build_status is 2
ERROR: Unable to find trybot_image for master_513590_671853_671473_*457115_squawks-release_2017-09-21!
trybot_url:        https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/release/builds/15115

which contains the "trybot_url". 
Can we put that link in the message to sheriff to avoid the sheriff several steps?

Alterantively, the cros trybot invocation has a --remote-description. Is there a way to find the builder based on that description? we could change the description to make this easier to find.


 
Project Member

Comment 1 by bugdroid1@chromium.org, Sep 29 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/toolchain-utils/+/cdd1907fbc70663a258f5d61d27668cd0823a51a

commit cdd1907fbc70663a258f5d61d27668cd0823a51a
Author: Yunlian Jiang <yunlian@google.com>
Date: Fri Sep 29 19:02:07 2017

buildbot_test_toolchain: return 2 if trybot fails.

We will print out the trybot url in the sheriff email if the trybot
fails. To to that, we need to set return value to 2 if the trybot
fails.

BUG=chromium:767524
TEST=None

Change-Id: Id3a8eb2cbcb8f85ada28ea11d4faf9113c9369ba
Reviewed-on: https://chromium-review.googlesource.com/692620
Commit-Ready: Yunlian Jiang <yunlian@chromium.org>
Tested-by: Yunlian Jiang <yunlian@chromium.org>
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>

[modify] https://crrev.com/cdd1907fbc70663a258f5d61d27668cd0823a51a/buildbot_test_toolchains.py

Components: Infra

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

Components: -Infra Infra>Client>ChromeOS
[It appears that a bunch of old cros issues bulk-added the "Infra" component recently, but they should probably be "Infra>Client>ChromeOS".]
Components: -Infra>Client>ChromeOS
Components: Tools>ChromeOS-Toolchain
This bug had an unsupported status. Updating to Untriaged so someone will reevaluate.
Status: Untriaged

Sign in to add a comment