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

Issue 614516 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: Apr 2017
Cc:
█ fdeng@chromium.org
dgarr...@chromium.org
puthik@chromium.org
█ slavamn@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

provision_AutoUpdate.double gets aborted

Project Member Reported by kevcheng@chromium.org, May 24 2016 
This is to concentrate efforts on  crbug.com/593423  (HWTest failure: provision_AutoUpdate.double,None (ABORT: None))

Looking specifically at https://uberchromegw.corp.google.com/i/chromeos/builders/wolf-paladin/builds/11125

Essentially it looks like the provision_AutoUpdate.double test can run slow and get aborted (although I don't see any mention of a timeout).

From https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/64398302-chromeos-test/chromeos4-row1-rack4-host1/

.parse.log shows that it starts May 23 22:42:29 and gets aborted 2016-05-23 23:03:23, 21 mins? weird timeout.

In the autoserv.DEBUG,  I see that there are two steps that take longer than I'd expect:

05/23 22:44:07.817 DEBUG|        base_utils:0269| [stdout] Downloading stateful payload from http://100.107.160.2:8082/static/wolf-paladin/R53-8365.0.0-rc2/stateful.tgz
05/23 22:44:08.070 DEBUG|        base_utils:0269| [stdout]   HTTP/1.1 200 OK
05/23 22:44:08.070 DEBUG|        base_utils:0269| [stdout]   Date: Tue, 24 May 2016 05:44:07 GMT
05/23 22:44:08.070 DEBUG|        base_utils:0269| [stdout]   Server: Apache/2.2.22 (Ubuntu)
05/23 22:44:08.071 DEBUG|        base_utils:0269| [stdout]   Last-Modified: Tue, 24 May 2016 05:20:25 GMT
05/23 22:44:08.071 DEBUG|        base_utils:0269| [stdout]   ETag: "e42cf3-ed0bfc9-5338fb6ee5f29"
05/23 22:44:08.071 DEBUG|        base_utils:0269| [stdout]   Accept-Ranges: bytes
05/23 22:44:08.071 DEBUG|        base_utils:0269| [stdout]   Content-Length: 248561609
05/23 22:44:08.072 DEBUG|        base_utils:0269| [stdout]   Keep-Alive: timeout=60, max=1000
05/23 22:44:08.072 DEBUG|        base_utils:0269| [stdout]   Connection: Keep-Alive
05/23 22:44:08.072 DEBUG|        base_utils:0269| [stdout]   Content-Type: application/x-gzip
05/23 22:51:54.302 DEBUG|        base_utils:0269| [stdout] Downloading command returns code 0.
05/23 22:51:54.302 DEBUG|        base_utils:0269| [stdout] Successfully downloaded update.
05/23 22:51:54.303 DEBUG|        base_utils:0269| [stdout] Restoring state to factory_install with dev_image.
05/23 23:02:38.669 DEBUG|        base_utils:0269| [stdout] [0523/230238:INFO:update_engine_client.cc(224)] Update succeeded -- reboot needed.

A passing run of this test only takes 9 mins (I could only find a suite that ran this test) while the failed run took > 20 mins.
https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/64458184-chromeos-test/hostless/

Comment 1 by kevcheng@chromium.org, May 28 2016 

Happened again: https://uberchromegw.corp.google.com/i/chromeos/builders/veyron_mighty-paladin/builds/2066

The aborted provision_AutoUpdate.double run is a bit weird, everything passes and finishes by May 21 22:26:24 but gets aborted 2016-05-21 22:46:52:

START	provision_AutoUpdate.double	provision_AutoUpdate.double	timestamp=1463894685	localtime=May 21 22:24:45	
	START	----	----	timestamp=1463894720	localtime=May 21 22:25:20	
		GOOD	----	sysinfo.before	timestamp=1463894720	localtime=May 21 22:25:20	
	END GOOD	----	----	timestamp=1463894720	localtime=May 21 22:25:20	
	START	----	----	timestamp=1463894736	localtime=May 21 22:25:36	
		GOOD	----	sysinfo.iteration.before	timestamp=1463894736	localtime=May 21 22:25:36	
	END GOOD	----	----	timestamp=1463894736	localtime=May 21 22:25:36	
	START	----	reboot	timestamp=1463894747	localtime=May 21 22:25:47	
		GOOD	----	reboot.start	timestamp=1463894747	localtime=May 21 22:25:47	
		GOOD	----	reboot.verify	timestamp=1463894783	localtime=May 21 22:26:23	
	END GOOD	----	reboot	kernel=3.14.0	localtime=May 21 22:26:24	timestamp=1463894784	
INFO	----	----	Job aborted by autotest_system on 2016-05-21 22:46:52

Comment 2 by steve...@chromium.org, Jul 1 2016

Cc: fdeng@chromium.org
Components: Infra>Client>ChromeOS
Labels: -Pri-3 Build-PFQ-Failures OS-Chrome Pri-1
Another failure:
https://uberchromegw.corp.google.com/i/chromeos/builders/tricky-chrome-pfq/builds/2034

Comment 3 by autumn@chromium.org, Jul 6 2016

Status: Unconfirmed (was: Untriaged)

Comment 4 by michae...@chromium.org, Apr 27 2017

Status: Archived (was: Unconfirmed)
 crbug.com/593423  is fixed...
►

Sign in to add a comment