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

Issue 728098 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

master-nyc-android-pfq and master-android-pfq failing on cbuildbot step

Project Member Reported by mtomasz@chromium.org, May 31 2017

Issue description

https://uberchromegw.corp.google.com/i/chromeos/waterfall?show=master-android-pfq

Log:
https://uberchromegw.corp.google.com/i/chromeos/builders/master-android-pfq/builds/3190/steps/cbuildbot%20%5Bmaster-android-pfq%5D/logs/stdio

(...)
03:00:33: INFO: Attempting refresh to obtain initial access_token
03:00:33: INFO: Refreshing access_token
03:01:33: INFO: Finished waiting for ts_mon process.
cbuildbot_launch: Unhandled exception:
Traceback (most recent call last):
  File "/b/build/slave/master-android-pfq-master/build/chromite/scripts/cbuildbot_launch", line 168, in <module>
    DoMain()
  File "/b/build/slave/master-android-pfq-master/build/chromite/scripts/cbuildbot_launch", line 164, in DoMain
    commandline.ScriptWrapperMain(FindTarget)
  File "/b/build/slave/master-android-pfq-master/build/chromite/lib/commandline.py", line 837, in ScriptWrapperMain
    ret = target(argv[1:])
  File "/b/build/slave/master-android-pfq-master/build/chromite/scripts/cbuildbot_launch.py", line 322, in main
    return _main(argv)
  File "/b/build/slave/master-android-pfq-master/build/chromite/scripts/cbuildbot_launch.py", line 302, in _main
    git_cache_dir=git_cache_dir)
  File "/b/build/slave/master-android-pfq-master/build/chromite/cbuildbot/repository.py", line 282, in __init__
    % self.directory)
ValueError: Given directory /b/cbuild/repository is not the root of a repository.
 

Comment 1 by pho...@chromium.org, May 31 2017

Status: Available (was: Unconfirmed)
master-paladin was also crashlooping last night with the same error. It seems to have corrected itself.

Comment 2 by lpique@chromium.org, May 31 2017

It does look like it is now fixed. Build 3192 was green.

https://uberchromegw.corp.google.com/i/chromeos/builders/master-android-pfq/builds/3192

master-nyc-android-pfq encountered the same error in builds 154 and 155, but 156 has gotten past that failure.

https://uberchromegw.corp.google.com/i/chromeos/builders/master-nyc-android-pfq/builds/156

Closing as fixed.

Comment 3 by lpique@chromium.org, May 31 2017

Status: WontFix (was: Available)

Comment 4 by pho...@chromium.org, May 31 2017

Cc: dgarr...@chromium.org
Status: Fixed (was: WontFix)
This was caused by a bug in cbuildbot_launch, which was reverted.

Comment 5 by dchan@chromium.org, Aug 1 2017

Labels: VerifyIn-61

Comment 6 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Sign in to add a comment