New issue
Advanced search Search tips
Starred by 1 user
Status: Fixed
Owner:
Closed: Aug 31
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment
poppy-release builds failing due to swarming timeout
Project Member Reported by kitching@google.com, Aug 29 Back to list
These seem to happen in different stages.

#696 is in PaygenTestCanary:

06:13:26: INFO: RunCommand: /b/c/cbuild/repository/chromite/third_party/swarming.client/swarming.py run --swarming chromeos-proxy.appspot.com --task-summary-json /tmp/cbuildbot-tmpauQqL3/tmpOx9vXY/temp_summary.json --raw-cmd --task-name poppy-release/R62-9886.0.0-paygen_au_canary --dimension os Ubuntu-14.04 --dimension pool default --print-status-updates --timeout 14400 --io-timeout 14400 --hard-timeout 14400 --expiration 1200 '--tags=priority:Build' '--tags=suite:paygen_au_canary' '--tags=build:poppy-release/R62-9886.0.0' '--tags=task_name:poppy-release/R62-9886.0.0-paygen_au_canary' '--tags=board:poppy' -- /usr/local/autotest/site_utils/run_suite.py --build poppy-release/R62-9886.0.0 --board poppy --suite_name paygen_au_canary --pool bvt --file_bugs True --priority Build --timeout_mins 180 --retry True --suite_min_duts 2 --job_keyvals "{'cidb_build_stage_id': 54236628L, 'cidb_build_id': 1795258, 'datastore_parent_key': ('Build', 1795258, 'BuildStage', 54236628L)}" -m 137953788
06:15:40: INFO: Refreshing due to a 401 (attempt 1/2)
06:15:40: INFO: Refreshing access_token
06:18:14: INFO: Refreshing due to a 401 (attempt 1/2)
06:18:14: INFO: Refreshing access_token
07:13:36: INFO: Refreshing due to a 401 (attempt 1/2)
07:13:36: INFO: Refreshing access_token
07:15:44: INFO: Refreshing due to a 401 (attempt 1/2)
07:15:44: INFO: Refreshing access_token
07:18:20: INFO: Refreshing due to a 401 (attempt 1/2)
07:18:20: INFO: Refreshing access_token
08:14:40: INFO: Refreshing due to a 401 (attempt 1/2)
08:14:41: INFO: Refreshing access_token
08:16:48: INFO: Refreshing due to a 401 (attempt 1/2)
08:16:48: INFO: Refreshing access_token
08:19:27: INFO: Refreshing due to a 401 (attempt 1/2)
08:19:27: INFO: Refreshing access_token
08:36:57: WARNING: Killing tasks: [<_BackgroundTask(_BackgroundTask-7:6:7:3, started)>]
08:36:57: WARNING: Killing 11292 (sig=24 SIGXCPU)

#697 passed.

#698 is in HWTest:

20:42:25: INFO: RunCommand: /b/c/cbuild/repository/chromite/third_party/swarming.client/swarming.py run --swarming chromeos-proxy.appspot.com --task-summary-json /tmp/cbuildbot-tmpI48HuI/tmpRMZNnq/temp_summary.json --raw-cmd --task-name poppy-release/R62-9888.0.0-bvt-inline --dimension os Ubuntu-14.04 --dimension pool default --print-status-updates --timeout 14400 --io-timeout 14400 --hard-timeout 14400 --expiration 1200 '--tags=priority:Build' '--tags=suite:bvt-inline' '--tags=build:poppy-release/R62-9888.0.0' '--tags=task_name:poppy-release/R62-9888.0.0-bvt-inline' '--tags=board:poppy' -- /usr/local/autotest/site_utils/run_suite.py --build poppy-release/R62-9888.0.0 --board poppy --suite_name bvt-inline --pool bvt --num 6 --file_bugs True --priority Build --timeout_mins 180 --retry True --max_retries 5 --minimum_duts 4 --suite_min_duts 6 --offload_failures_only False --job_keyvals "{'cidb_build_stage_id': 54305064L, 'cidb_build_id': 1797501, 'datastore_parent_key': ('Build', 1797501, 'BuildStage', 54305064L)}" -m 138080437
23:06:27: WARNING: Killing tasks: [<_BackgroundTask(_BackgroundTask-7:7:4, started)>]
23:06:27: WARNING: Killing 28085 (sig=24 SIGXCPU)
 
Cc: jrbarnette@chromium.org
Labels: OS-Chrome
Cc: xixuan@chromium.org
Status: Fixed
We recently discovered that many swarming bots were dead.

I believe this is fixed now.
Sign in to add a comment