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

Issue 711430 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Apr 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

[cbuildbot] --remote-description value is getting overwritten with 'buildbucket'

Project Member Reported by cmt...@chromium.org, Apr 13 2017

Issue description

This is a recent change/error in the cbuildbot mechanism.

Until Monday (April 10), if you launch a remote cbuildbot with the '--remote-description' flag, the value of your remote description got stored with the trybot job as the 'reason'.  As of Tuesday, regardless of what remote description you give, the 'reason' becomes 'buildbucket'.

This can be worked around by adding '--do-not-use-buildbucket' to the trybot jobs, but this is not generally recommended.

Below are the links for two examples I launched, the first without the workaround, and the second with, and BOTH with the same --remote-description flag.  If you look at the 'reason' field in the first, it says 'buildbucket'.  If you look at the reason field in the second, it matches my remote description value.

$ ./cbuildbot --remote --nochromesdk --notests --remote-description=master_419149_daisy-release_2017-04-13 --latest-toolchain  -g '419149' daisy-release
Verifying patches...
Submitting tryjob...
Successfully sent PUT request to [buildbucket_bucket:master.chromiumos.tryserver] with [config:daisy-release] [buildbucket_id:8982396654700124352].
Tryjob submitted!
$ ./cbuildbot --remote --nochromesdk --notests --remote-description=master_419149_daisy-release_2017-04-13 --latest-toolchain  -g '419149' daisy-release --do-not-use-buildbucket
Verifying patches...
Submitting tryjob...
Tryjob submitted!

https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/release/builds/10473
https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/release/builds/10474


 
Project Member

Comment 1 by bugdroid1@chromium.org, Apr 13 2017

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

commit 3f17e3d5880b0b8cd328b08b0e793783264e125a
Author: Caroline Tice <cmtice@google.com>
Date: Thu Apr 13 22:37:06 2017

[toolchain-utils] Workaround for new bug in cbuildbot.

There's a regression/bug in the cbuildbot stuff that is causing
all of our cbuildbot jobs to be unable to find their build records,
which causes them to fail.  Adding the flag '--do-not-use-buildbucket'
is a workaround that temporarily fixes this problem.  This CL adds
that flag to all of our cbuildbot jobs.

BUG= chromium:711430 
TEST=Launched cbuildbots with & without this flag; saw the problem without
the flag; with the flag the problme was gone.

Change-Id: I75219dad55e762ce2d5f0e3b6d885a8e91be014e
Reviewed-on: https://chromium-review.googlesource.com/477391
Commit-Ready: Caroline Tice <cmtice@chromium.org>
Tested-by: Caroline Tice <cmtice@chromium.org>
Reviewed-by: Yunlian Jiang <yunlian@chromium.org>

[modify] https://crrev.com/3f17e3d5880b0b8cd328b08b0e793783264e125a/cros_utils/buildbot_utils.py

Project Member

Comment 2 by bugdroid1@chromium.org, Apr 13 2017

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

commit 3f17e3d5880b0b8cd328b08b0e793783264e125a
Author: Caroline Tice <cmtice@google.com>
Date: Thu Apr 13 22:37:06 2017

[toolchain-utils] Workaround for new bug in cbuildbot.

There's a regression/bug in the cbuildbot stuff that is causing
all of our cbuildbot jobs to be unable to find their build records,
which causes them to fail.  Adding the flag '--do-not-use-buildbucket'
is a workaround that temporarily fixes this problem.  This CL adds
that flag to all of our cbuildbot jobs.

BUG= chromium:711430 
TEST=Launched cbuildbots with & without this flag; saw the problem without
the flag; with the flag the problme was gone.

Change-Id: I75219dad55e762ce2d5f0e3b6d885a8e91be014e
Reviewed-on: https://chromium-review.googlesource.com/477391
Commit-Ready: Caroline Tice <cmtice@chromium.org>
Tested-by: Caroline Tice <cmtice@chromium.org>
Reviewed-by: Yunlian Jiang <yunlian@chromium.org>

[modify] https://crrev.com/3f17e3d5880b0b8cd328b08b0e793783264e125a/cros_utils/buildbot_utils.py

Comment 3 by nxia@chromium.org, Apr 13 2017

Owner: cmt...@chromium.org
cmtice@, you can find the description in the Build Properties (the bottom of the build page) in the "name" row. 

https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/release/builds/10474

Comment 5 by cmt...@chromium.org, Apr 14 2017

Ok, I will try to find/use that field in the build records.  Thanks!
Project Member

Comment 6 by bugdroid1@chromium.org, Apr 14 2017

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

commit 466c45d752af98dae774ecd85c1b07349c292cd9
Author: Caroline Tice <cmtice@google.com>
Date: Fri Apr 14 19:25:28 2017

[toolchain-utils] Remove --do-not-use-buildbucket flag

This implements the correct way to find the remote description so
that we do not need to disable the buildbucket authentication.

BUG= chromium:711430 
TEST=Launched nightly buildbot job and it was able to find correct
build log.

Change-Id: I0a2e16ec284bae46af684daf3abcbbea1b9c3fe9
Reviewed-on: https://chromium-review.googlesource.com/478010
Commit-Ready: Caroline Tice <cmtice@chromium.org>
Tested-by: Caroline Tice <cmtice@chromium.org>
Reviewed-by: Yunlian Jiang <yunlian@chromium.org>

[modify] https://crrev.com/466c45d752af98dae774ecd85c1b07349c292cd9/cros_utils/buildbot_utils.py

Comment 7 by cmtice@google.com, Apr 18 2017

Status: Verified (was: Untriaged)

Sign in to add a comment