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

Issue 853614 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jun 2018
Cc:
█ jbrandmeyer@chromium.org
mojahsu@chromium.org
grundler@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----



Sign in to add a comment

cbuildbot_launch "GET /computeMetadata/v1/instance/zone HTTP/1.1" 200 41

Project Member Reported by mojahsu@chromium.org, Jun 18 2018 
DEBUG: "GET /computeMetadata/v1/instance/zone HTTP/1.1" 200 41
step returned non-zero exit code: 1

Link to build or pfq page.
https://uberchromegw.corp.google.com/i/chromeos/builders/kahlee-paladin/builds/2388
https://uberchromegw.corp.google.com/i/chromeos/builders/kahlee-paladin/builds/2389
https://uberchromegw.corp.google.com/i/chromeos/builders/kahlee-paladin/builds/2390


in  cbuildbot_launch [kahlee-paladin]
full environment:
 AWS_CREDENTIAL_FILE: /b/build/site_config/.boto
 BOTO_CONFIG: /b/build/site_config/.boto
 BUILDBOT_BLAMELIST: []
 BUILDBOT_BRANCH: 
 BUILDBOT_BUILDBOTURL: https://uberchromegw.corp.google.com/i/chromeos/
 BUILDBOT_BUILDERNAME: kahlee-paladin
 BUILDBOT_BUILDNUMBER: 2388
 BUILDBOT_CLOBBER: 
 BUILDBOT_GOT_REVISION: None
 BUILDBOT_MASTERNAME: chromeos
 BUILDBOT_REVISION: 
 BUILDBOT_SCHEDULER: None
 BUILDBOT_SLAVENAME: cros-beefy455-c2
 CHROME_HEADLESS: 1
 CIPD_CACHE_DIR: /b/c/cipd
 DEPOT_TOOLS_UPDATE: 0
 DISPLAY: :0.0
 GIT_USER_AGENT: git/2.11.0 linux2 cros-beefy455-c2.c.chromeos-bot.internal
 HOME: /home/chrome-bot
 INFRA_BUILDBOT_MASTER_CLASS_NAME: ChromeOS
 INFRA_BUILDBOT_SLAVE_ACTIVE_SUBDIR: 
 INFRA_BUILDBOT_SLAVE_NAME: cros-beefy455-c2
 LANG: en_US.UTF-8
 LOGDOG_COORDINATOR_HOST: logs.chromium.org
 LOGDOG_STREAM_PREFIX: bb/chromeos/kahlee-paladin/2388
 LOGDOG_STREAM_PROJECT: chromeos
 LOGDOG_STREAM_SERVER_PATH: unix:/b/build/rr/tmpho0DFk/butler.sock
 PAGER: cat
 PATH: /b/cipd_client:/b/cipd_path_tools:/b/cipd_path_tools/bin:/b/rr/tmpTa9Gc0/w/depot_tools:/b/cipd_path_tools:/b/cipd_path_tools/bin:/b/cipd_client:/home/chrome-bot/slavebin:/b/depot_tools:/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin
 PWD: /b/build/slave/kahlee-paladin-master/build
 PYTHONIOENCODING: UTF-8
 PYTHONPATH: /b/build/site_config:/b/build/scripts:/b/build/scripts/release:/b/build/third_party:/b/build/third_party/google_api_python_client:/b/build/third_party/httplib2/python2:/b/build/third_party/infra_libs:/b/build/third_party/oauth2client:/b/build/third_party/pyasn1:/b/build/third_party/pyasn1-modules:/b/build/third_party/python-rsa:/b/build/third_party/requests_2_10_0:/b/build/third_party/setuptools-0.6c11:/b/build/third_party/site-packages:/b/build/third_party/uritemplate:/b/build_internal/site_config:/b/build_internal/symsrc:/b/build/slave:/b/build/third_party/buildbot_slave_8_4:/b/build/third_party/twisted_10_2:
 PYTHONUNBUFFERED: 1
 TESTING_SLAVENAME: cros-beefy455-c2
 USER: chrome-bot
 USERNAME: chrome-bot
 VPYTHON_CLEAR_PYTHONPATH: 1
 VPYTHON_VIRTUALENV_ROOT: /b/c/vpython
14:19:19: INFO: Starting new HTTP connection (1): metadata.google.internal
14:19:19: DEBUG: "GET /computeMetadata/v1/instance/zone HTTP/1.1" 200 41
step returned non-zero exit code: 1

Comment 6 by mojahsu@chromium.org, Jun 19 2018

Cc: -rrangel@chromium.org grundler@chromium.org
Components: Infra>Client>ChromeOS

Comment 7 by uekawa@google.com, Jun 19 2018 

re #4 I don't understand, they look very different.


https://uberchromegw.corp.google.com/i/chromeos/builders/master-nyc-android-pfq/builds/2459
is 
cyan-nyc-android-pfq: The HWTest [bvt-arc] stage failed: ** HWTest failed (code 1) **

which is https://luci-milo.appspot.com/buildbot/chromeos/cyan-nyc-android-pfq/2239 which is [Test-History]: cheets_StartAndroid.stress failure.







https://uberchromegw.corp.google.com/i/chromeos/builders/caroline-arcnext-chrome-pfq/builds/578
Link to suite
[Test-Logs]: cheets_CTS_P.9.0_r1.x86.CtsAccelerationTestCases: retry_count: 1, GOOD: completed successfully
[Test-History]: cheets_CTS_P.9.0_r1.x86.CtsAccelerationTestCases
[Test-Logs]: cheets_CTS_P.9.0_r1.x86.CtsAdminTestCases: retry_count: 2, GOOD: completed successfully
[Test-History]: cheets_CTS_P.9.0_r1.x86.CtsAdminTestCases
[Test-Logs]: cheets_GTS_P.6.0_r1.GtsAdminTestCases: retry_count: 2, ERROR: Command failed, rc=1, Command returned non-zero exit status
[Test-History]: cheets_GTS_P.6.0_r1.GtsAdminTestCases
Suite details

Comment 8 by la...@chromium.org, Jun 19 2018

Status: WontFix (was: Untriaged)
Failures of the cbuildbot_launch step are generally not relevant; most of the other build steps happen within cbuildbot_launch and an unfortunate feature of the build UI is that the cbuildbot_launch step appears to have failed when it was actually a child process that failed.
►

Sign in to add a comment