Issue 619112 link

Starred by 1 user

Issue metadata

Status:	Archived
Owner:	xixuan@chromium.org
Closed:	Oct 2016
Cc:	█ dshi@chromium.org akes...@chromium.org █ shuqianz@chromium.org █ jrbarnette@chromium.org
Components:	Infra>Client>ChromeOS
EstimatedDays:	----
NextAction:	----
OS:	Chrome
Pri:	2
Type:	----
VerifyIn-56 VerifyIn-57 VerifyIn-58 VerifyIn-59 VerifyIn-60 VerifyIn-61

Extend the timeout_min for suite_job in test_push

Project Member Reported by xixuan@chromium.org, Jun 10 2016

Issue description

The current timeout_min for suite_job is 24 mins. But it's found that the quawks DUT needs repair and provision before it can run any job. Repair seems last about 10+ mins and provision lasts about 10- mins, which make 24 mins a little bit hard for finishing all the suite jobs. I checked some completed jobs, seems many of them complete just before the hard deadline: 24 mins.

Not sure why different builds may lead to different repair processes. It takes time to investigate. Can we first temporarily make the timeout_min longer to avoid such errors?

Project Member

Comment 1 by bugdroid1@chromium.org, Jun 14 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/2d66858a2d1b03cca733bc68507bb45f07a89c40

commit 2d66858a2d1b03cca733bc68507bb45f07a89c40
Author: xixuan <xixuan@google.com>
Date: Fri Jun 10 21:02:32 2016

Autotest: extend the timeout limit for suite job in test push.

This CL extend the timeout limit for suite job from 24 mins to 30 mins to
reduce 'timeout error' in test push.

BUG= chromium:619112 
TEST=None

Change-Id: Ibcd998cb846cbc742601d137114b8f9416f68e41
Reviewed-on: https://chromium-review.googlesource.com/351482
Commit-Ready: Xixuan Wu <xixuan@chromium.org>
Tested-by: Xixuan Wu <xixuan@chromium.org>
Reviewed-by: Dan Shi <dshi@google.com>

[modify] https://crrev.com/2d66858a2d1b03cca733bc68507bb45f07a89c40/site_utils/test_push.py