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

Issue 595760 link

Starred by 1 user
Status: Verified
Owner:
█ dshi@chromium.org
Last visit > 30 days ago
Closed: Mar 2016
Cc:
dchan@chromium.org
█ waihong@chromium.org
█ shchen@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

nightly jobs are being killed in less than 24 hours

Project Member Reported by shchen@chromium.org, Mar 17 2016 
faft_bios_tot/faft_ec_tot tests are being aborted in less than 24 hours.

For example, looking at http://cautotest/afe/#tab_id=view_job&object_id=56793707, it was created at:

2016-03-15 16:05:23

but the first job seems to have only started at (even though the machine was free):

START	56842067-chromeos-test/chromeos1-row1-rack9-host6/firmware_FwScreenCloseLid.dev	firmware_FwScreenCloseLid.dev	timestamp=1458121244	localtime=Mar 16 02:40:44

and it seems that the jobs were aborted at (consistent with the actual job start time):

ABORT	----	veyron_jerry-release/R51-8064.0.0/faft_bios_tot/firmware_CorruptFwSigB.dev	timestamp=1458169629	localtime=Mar 16 16:07:09

Also, since faft_ec_tot is created at the same time as faft_bios_tot, all the tests for faft_ec_tot got aborted as well because they timed out.  Is there any way that we can figure out why there was a 10 hour delay before jobs started?
Project Member

Comment 1 by bugdroid1@chromium.org, Mar 17 2016 

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

commit 130ca2d74307547989a0e84db3e84505352f7759
Author: Shelley Chen <shchen@chromium.org>
Date: Thu Mar 17 17:19:06 2016

suite_scheduler: Moving up start time of faft_ec_tot

faft_ec_tot nightly test is aborting due to timeout because
faft_bios_tot is timing out.  Moving faft_ec_tot start time 8
hours earlier to prevent this resource conflict.

BUG= chromium:595760 
BRANCH=None
TEST=site_utils/suite_scheduler/suite_scheduler.py --sanity

Change-Id: I9867881544ed19d564455d107cfb17906e093666
Signed-off-by: Shelley Chen <shchen@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/333400
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Dan Shi <dshi@google.com>

[modify] https://crrev.com/130ca2d74307547989a0e84db3e84505352f7759/suite_scheduler.ini
Project Member

Comment 2 by bugdroid1@chromium.org, Mar 17 2016 

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

commit 4de6fb3550e4fb006207b00261fd9ee80ce4b721
Author: Dan Shi <dshi@google.com>
Date: Thu Mar 17 18:49:49 2016

[autotest] Update timeout settings in suite scheduler before creating suite job

BUG= chromium:595760 
TEST=local suite scheduler run, confirm timeout settings are updated.

Change-Id: I38fc1e0eae498e59c273e9f51f687a650c527cc7
Reviewed-on: https://chromium-review.googlesource.com/333671
Commit-Ready: Dan Shi <dshi@google.com>
Tested-by: Dan Shi <dshi@google.com>
Reviewed-by: Kevin Cheng <kevcheng@chromium.org>

[modify] https://crrev.com/4de6fb3550e4fb006207b00261fd9ee80ce4b721/site_utils/suite_scheduler/deduping_scheduler.py
[modify] https://crrev.com/4de6fb3550e4fb006207b00261fd9ee80ce4b721/site_utils/suite_scheduler/deduping_scheduler_unittest.py

Comment 3 by dshi@chromium.org, Mar 17 2016

Status: Fixed (was: Untriaged)

Comment 4 by patricia@chromium.org, Apr 11 2016

Labels: VerifyIn-51

Comment 5 by patricia@chromium.org, May 23 2016

Status: Verified (was: Fixed)
Bulk verified
►

Sign in to add a comment