PFQ failures with "Refreshing due to a 401" / "Refreshing access_token" messages |
|||||
Issue descriptionThere are several failure detected: https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/tricky-tot-chrome-pfq-informational/builds/1599/steps/HWTest%20%5Bbvt-inline%5D/logs/stdio https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/peach_pit-tot-chrome-pfq-informational/builds/2355/steps/HWTest%20%5Bbvt-inline%5D/logs/stdio https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/cyan-cheets-tot-chrome-pfq-cheets-informational/builds/573 They happened in near the same time and contain following log: 08-01-2016 [05:47:01] Submitted create_suite_job rpc 08-01-2016 [05:47:14] Created suite job: http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=71714107 @@@STEP_LINK@Link to suite@http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=71714107@@@ --create_and_return was specified, terminating now. Will return from run_suite with status: OK 05:47:16: INFO: RunCommand: /b/cbuild.peach_pit/chromite/third_party/swarming.client/swarming.py run --swarming chromeos-proxy.appspot.com --task-summary-json /tmp/cbuildbot-tmphi2VnA/tmpGIJx11/temp_summary.json --raw-cmd --task-name peach_pit-tot-chrome-pfq-informational/R54-8661.0.0-b2355-bvt-inline --dimension os Ubuntu-14.04 --dimension pool default --print-status-updates --timeout 14400 --io-timeout 14400 --hard-timeout 14400 --expiration 1200 -- /usr/local/autotest/site_utils/run_suite.py --build peach_pit-tot-chrome-pfq-informational/R54-8661.0.0-b2355 --board peach_pit --suite_name bvt-inline --pool continuous --num 6 --file_bugs True --priority PFQ --timeout_mins 180 --retry False --minimum_duts 4 --offload_failures_only False -m 71714107 06:31:55: INFO: Refreshing due to a 401 (attempt 1/2) 06:31:55: INFO: Refreshing access_token 06:36:41: INFO: Refreshing due to a 401 (attempt 1/2) 06:36:41: INFO: Refreshing access_token 07:31:55: INFO: Refreshing due to a 401 (attempt 1/2) 07:31:55: INFO: Refreshing access_token 07:36:41: INFO: Refreshing due to a 401 (attempt 1/2) 07:36:41: INFO: Refreshing access_token 08:11:17: WARNING: Killing tasks: [<_BackgroundTask(_BackgroundTask-5:7:2, started)>] 08:11:17: WARNING: Killing 33657 (sig=24 SIGXCPU) 08:11:17: WARNING: RunCommand: pstree -Apals 33657 08:11:17: WARNING: (stdout):
,
Aug 1 2016
There are a few places where we have "Refreshing due to a" ... in the code, mostly in oauth2client, but I think this is probably coming from catapult? Ultimately these are all failing with "Could not attach to process", which is similar to they symptoms of issue 623880, however the INFO and WARNING messages (which I think come from test_stages.py in chromite?) may be indicating the root cause here, in which case we should fail with a more obvious error message sooner. +bpastene@ (the current infra trooper) and others who may have better insight.
,
Sep 1 2016
,
Sep 4 2017
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. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 5 2017
obsolete |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by khmel@chromium.org
, Aug 1 2016