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

Issue 643871 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 593423
Owner: ----
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

provision_AutoUpdate.double occasionally takes a long time

Project Member Reported by lpique@chromium.org, Sep 3 2016

Issue description

This was the cause of some test failures ( crbug.com/593423 ) when the test suite deadline was reached when running this test.

For the most part it runs under the twenty minute deadline. When it was failing, it looked like it was being SIGTERM'ed right as it was finishing up.

For now I'm increasing the deadline ("max-runtime-mins") set for the two suites where the test is run -- bvt-inline and push_to_prod.
 
Cc: fdeng@chromium.org josephsih@chromium.org xixuan@chromium.org pho...@chromium.org jdiez@chromium.org aga...@chromium.org
Labels: -Pri-3 Pri-1
I've seen a few cases of this failing on more builds recently. Right now we're seeing it on Lumpy, Link, and Wolf. The symptom seems rather vague, though.

From https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/76184253-chromeos-test/hostless/debug/ :
09/08 20:07:30.346 DEBUG|             suite:1095| Adding status keyval for login_RetrieveActiveSessions=76184363-chromeos-test
09/08 20:22:04.674 INFO |        server_job:0129| START	----	link-paladin/R55-8784.0.0-rc1/bvt-inline/provision_AutoUpdate.double	timestamp=1473391324	localtime=Sep 08 20:22:04	
09/08 20:22:04.675 INFO |        server_job:0129| 	ABORT	----	link-paladin/R55-8784.0.0-rc1/bvt-inline/provision_AutoUpdate.double	timestamp=1473391324	localtime=Sep 08 20:22:04	
09/08 20:22:04.675 INFO |        server_job:0129| END ABORT	----	link-paladin/R55-8784.0.0-rc1/bvt-inline/provision_AutoUpdate.double	timestamp=1473391324	localtime=Sep 08 20:22:04	
09/08 20:22:09.701 DEBUG|     dynamic_suite:0556| Finished waiting on suite. Returning from _perform_reimage_and_run.

If I'm reading this right it took about 14 minutes and 34 seconds to start the job, after which point it aborted right right away.
Looks like this might be a duplicate of  issue #593423 ?
Re: Comment#2: it is highly related. The test aborted for timeout.

Maybe mark this issue as a duplicate of  Issue 593423 ?

Comment 4 by lpique@chromium.org, Oct 14 2016

Mergedinto: 593423
Status: Duplicate (was: Untriaged)

Sign in to add a comment