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

Issue metadata

Status: Archived
Owner: ----
Closed: Jun 2017
EstimatedDays: ----
NextAction: ----
OS: Linux , Chrome
Pri: 3
Type: Bug

Sign in to add a comment

vmtest timeout on ASAN bots

Project Member Reported by, Apr 24 2017 Back to list

Issue description

x86-generic-asan time out on vmtests, e.g.

There are no obvious failures, it seems we're just running too slowly and get killed by the 1 hour test timeout:

23:29:01: ERROR: Traceback (most recent call last):
  File "/b/cbuild/repository/chromite/cbuildbot/stages/", line 628, in Run
  File "/b/cbuild/repository/chromite/cbuildbot/stages/", line 213, in PerformStage
    self._RunTest(test_type, per_test_results_dir)
  File "/b/cbuild/repository/chromite/cbuildbot/stages/", line 199, in _RunTest
  File "/b/cbuild/repository/chromite/cbuildbot/", line 777, in RunTestSuite
    kill_timeout=10 * 60)
  File "/b/cbuild/repository/chromite/lib/", line 593, in RunCommand
    (cmd_result.output, cmd_result.error) = proc.communicate(input)
  File "/usr/lib/python2.7/", line 796, in communicate
  File "/usr/lib/python2.7/", line 1376, in wait
    pid, sts = _eintr_retry_call(os.waitpid,, 0)
  File "/usr/lib/python2.7/", line 476, in _eintr_retry_call
    return func(*args)
  File "/b/cbuild/repository/chromite/lib/", line 62, in kill_us
    raise TimeoutError(error_message % {'time': max_run_time})
TimeoutError: Timeout occurred- waited 3600 seconds. Reached VMTestStage test run timeout.

We'll need to investigate how to raise the timeout.

Comment 1 by, Apr 25 2017

+ deputy, seems like we might need to sheriff to look too
Labels: Hotlist-CrOS-Sheriffing

Comment 3 by, Jun 2 2017

Status: Archived

Sign in to add a comment