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

Issue 794682 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Suite aborted a test, but test still ran (4 minutes later)

Project Member Reported by dgarr...@chromium.org, Dec 13 2017

Issue description

This build:

https://luci-milo.appspot.com/buildbot/chromeos/cyan-paladin/4747

Ran this test suite:

https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/162143315-chromeos-test

Which launched this test:

https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/162163614-chromeos-test

The suite aborted the test (status.log):

...
START	162143337-chromeos-test/chromeos4-row6-rack9-host7/cheets_AndroidToChromeIntents	cheets_AndroidToChromeIntents	timestamp=1513139493	localtime=Dec 12 20:31:33	
	ABORT	162143337-chromeos-test/chromeos4-row6-rack9-host7/cheets_AndroidToChromeIntents	cheets_AndroidToChromeIntents	timestamp=1513143796	localtime=Dec 12 21:43:16	None
END ABORT	162143337-chromeos-test/chromeos4-row6-rack9-host7/cheets_AndroidToChromeIntents	cheets_AndroidToChromeIntents	timestamp=1513143796	localtime=Dec 12 21:43:16	
INFO	----	----	Job aborted by autotest_system on 2017-12-12 21:50:44


But the test still ran (status.log):

INFO	----	----	kernel=3.18.0-16360-g5ac3fc4fe855-dirty	localtime=Dec 12 21:47:23	timestamp=1513144043	
START	----	----	timestamp=1513144069	localtime=Dec 12 21:47:49	
	START	cheets_AndroidToChromeIntents	cheets_AndroidToChromeIntents	timestamp=1513144069	localtime=Dec 12 21:47:49	
		GOOD	cheets_AndroidToChromeIntents	cheets_AndroidToChromeIntents	timestamp=1513144142	localtime=Dec 12 21:49:02	completed successfully
	END GOOD	cheets_AndroidToChromeIntents	cheets_AndroidToChromeIntents	timestamp=1513144142	localtime=Dec 12 21:49:02	
END GOOD	----	----	timestamp=1513144145	localtime=Dec 12 21:49:05	
 
Cc: akes...@chromium.org jrbarnette@chromium.org
My understanding is that the child job should have been aborted.
From the build page, I see this in the test results:
    [Test-Logs]: cheets_AndroidToChromeIntents: retry_count: 1, GOOD: completed successfully

It seems the test was aborted, then retried, which would
be (mostly) WAI.  Still, there's a question as to why the
first test seems to have hung.

Status: WontFix (was: Untriaged)

Sign in to add a comment