New issue
Advanced search Search tips

Issue 878267 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Aug 31
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Android P PFQ is failing due to HWTest[sanity] timeout

Project Member Reported by niwa@chromium.org, Aug 28

Issue description

kevin-arcnext-pi-android-pfq failed 4 times in a row as of 2018-08-27 20:50 (PST)

In the latest 2 runs, HWTest[sanity] timed out due to "401" for kevin-arcnext. Other boards (caroline-arcnext, etc) look fine.

Setting priority to 1 since this is blocking Android P PFQ

https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8937010305667342704

Log : https://luci-logdog.appspot.com/v/?s=chromeos/buildbucket/cr-buildbucket.appspot.com/8937010305667342704/+/steps/HWTest__sanity_/0/stdout

https://paste.googleplex.com/5429779046072320
 
This is now happening on caroline-arcnext-pi-android-pfq / stage HWTest [bvt-arc]

https://cros-goldeneye.corp.google.com/chromeos/legoland/builderHistory?buildConfig=caroline-arcnext-pi-android-pfq&buildBranch=master

22:49:25: INFO: Re-run swarming_cmd to avoid buildbot salency check.
22:49:25: INFO: RunCommand: /b/swarming/w/ir/cache/cbuild/repository/chromite/third_party/swarming.client/swarming.py run --swarming chromeos-proxy.appspot.com --task-summary-json /b/swarming/w/ir/tmp/t/cbuildbot-tmpv95_kb/tmpvNRuiG/temp_summary.json --print-status-updates --timeout 18600 --raw-cmd --task-name caroline-arcnext-pi-android-pfq/R70-11018.0.0-rc2-bvt-arc --dimension os Ubuntu-14.04 --dimension pool default --io-timeout 18600 --hard-timeout 18600 --expiration 1200 '--tags=priority:PFQ' '--tags=suite:bvt-arc' '--tags=build:caroline-arcnext-pi-android-pfq/R70-11018.0.0-rc2' '--tags=task_name:caroline-arcnext-pi-android-pfq/R70-11018.0.0-rc2-bvt-arc' '--tags=board:caroline-arcnext' -- /usr/local/autotest/site_utils/run_suite.py --build caroline-arcnext-pi-android-pfq/R70-11018.0.0-rc2 --board caroline --suite_name bvt-arc --pool bvt --file_bugs True --priority PFQ --timeout_mins 250 --retry True --max_retries 5 --minimum_duts 3 --suite_min_duts 3 --offload_failures_only False --job_keyvals "{'cidb_build_stage_id': 90712632L, 'cidb_build_id': 2892564, 'datastore_parent_key': ('Build', 2892564, 'BuildStage', 90712632L)}" -m 232137639
23:40:55: INFO: Refreshing due to a 401 (attempt 1/2)
23:40:55: INFO: Refreshing access_token
23:44:25: INFO: Refreshing due to a 401 (attempt 1/2)
23:44:25: INFO: Refreshing access_token
23:46:33: INFO: Refreshing due to a 401 (attempt 1/2)
23:46:33: INFO: Refreshing access_token
00:26:26: INFO: Re-run swarming_cmd to avoid buildbot salency check.
00:26:26: INFO: RunCommand: /b/swarming/w/ir/cache/cbuild/repository/chromite/third_party/swarming.client/swarming.py run --swarming chromeos-proxy.appspot.com --task-summary-json /b/swarming/w/ir/tmp/t/cbuildbot-tmpv95_kb/tmpvNRuiG/temp_summary.json --print-status-updates --timeout 18600 --raw-cmd --task-name caroline-arcnext-pi-android-pfq/R70-11018.0.0-rc2-bvt-arc --dimension os Ubuntu-14.04 --dimension pool default --io-timeout 18600 --hard-timeout 18600 --expiration 1200 '--tags=priority:PFQ' '--tags=suite:bvt-arc' '--tags=build:caroline-arcnext-pi-android-pfq/R70-11018.0.0-rc2' '--tags=task_name:caroline-arcnext-pi-android-pfq/R70-11018.0.0-rc2-bvt-arc' '--tags=board:caroline-arcnext' -- /usr/local/autotest/site_utils/run_suite.py --build caroline-arcnext-pi-android-pfq/R70-11018.0.0-rc2 --board caroline --suite_name bvt-arc --pool bvt --file_bugs True --priority PFQ --timeout_mins 250 --retry True --max_retries 5 --minimum_duts 3 --suite_min_duts 3 --offload_failures_only False --job_keyvals "{'cidb_build_stage_id': 90712632L, 'cidb_build_id': 2892564, 'datastore_parent_key': ('Build', 2892564, 'BuildStage', 90712632L)}" -m 232137639
00:40:58: INFO: Refreshing due to a 401 (attempt 1/2)
00:40:58: INFO: Refreshing access_token
....
01:06:44: ERROR: Timeout occurred- waited 15626 seconds, failing. Timeout reason: This build has reached the timeout deadline set by the master. Either this stage or a previous one took too long (see stage timing historical summary in ReportStage) or the build failed to start on time.
01:06:44: ERROR: Timeout occurred- waited 15751 seconds, failing. Timeout reason: This build has reached the timeout deadline set by the master. Either this stage or a previous one took too long (see stage timing historical summary in ReportStage) or the build failed to start on time.

Mergedinto: 878403
Status: Duplicate (was: Untriaged)

Sign in to add a comment