New issue
Advanced search Search tips
Starred by 1 user
Status: Archived
Owner:
Closed: Nov 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment
x86-mario-release builder failed during paygen due to timeout
Project Member Reported by mcchou@chromium.org, Nov 28 2016 Back to list
15 out of 20 latest builds of x86-mario-release failed during paygen stage. See the latest three failures as follows.

https://uberchromegw.corp.google.com/i/chromeos/builders/x86-mario-release/builds/5463
https://uberchromegw.corp.google.com/i/chromeos/builders/x86-mario-release/builds/5462
https://uberchromegw.corp.google.com/i/chromeos/builders/x86-mario-release/builds/5461

stdout of Paygen:
07:42:33: INFO: RunCommand: /b/cbuild/internal_master/chromite/third_party/swarming.client/swarming.py run --swarming chromeos-proxy.appspot.com --task-summary-json /tmp/cbuildbot-tmp2WgqtJ/tmpAoTl3O/temp_summary.json --raw-cmd --task-name x86-mario-release/R57-9030.0.0-paygen_au_dev --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_dev' '--tags=build:x86-mario-release/R57-9030.0.0' '--tags=task_name:x86-mario-release/R57-9030.0.0-paygen_au_dev' '--tags=board:x86-mario' -- /usr/local/autotest/site_utils/run_suite.py --build x86-mario-release/R57-9030.0.0 --board x86-mario --suite_name paygen_au_dev --pool bvt --file_bugs True --priority Build --timeout_mins 180 --retry True --suite_min_duts 2 -m 87813846
09:50:44: ERROR: Timeout occurred- waited 27511 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.
09:50:44: INFO: Running cidb query on pid 29789, repr(query) starts with <sqlalchemy.sql.expression.Insert object at 0x3e08450>
09:50:44: ERROR: Timeout occurred- waited 27818 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.
09:50:45: INFO: Running cidb query on pid 29789, repr(query) starts with <sqlalchemy.sql.expression.Insert object at 0x4086fd0>

 
Comment 1 by dshi@chromium.org, Nov 28 2016
Status: Fixed
The suite timeout was caused by dut shortage. The problem is that x86-mario duts in bvt pools were shared with suites pool. I've removed pool:suites label from these duts. 
Comment 2 by dchan@google.com, Mar 4 2017
Labels: VerifyIn-58
Comment 3 by dchan@google.com, Apr 17 2017
Labels: VerifyIn-59
Comment 4 by dchan@google.com, May 30 2017
Labels: VerifyIn-60
Labels: VerifyIn-61
Status: Archived
Sign in to add a comment