New issue
Advanced search Search tips

Issue 749268 link

Starred by 1 user
Status: Duplicate
Merged: issue 750918
Owner: ----
Closed: Aug 2017
Cc:
derat@chromium.org
pwang@chromium.org
davidri...@chromium.org
ihf@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature



Sign in to add a comment

test-level retries for VMTest

Project Member Reported by akes...@chromium.org, Jul 26 2017 
Retrying all of VMTests stage if a single test failed is slow, as evidenced by for instance https://viceroy.corp.google.com/chromeos/build_details?build_config=betty-paladin&build_number=226

Instead, we can push simple retry logic into test_that (which is what runs VMTests, on builder).

Gotta be a bit careful how we do this so that we don't end making things worse (ie slower) by over-retrying.

Comment 1 by akes...@chromium.org, Jul 26 2017

Cc: davidri...@chromium.org

Comment 2 by davidri...@chromium.org, Jul 26 2017

Cc: derat@chromium.org
I assume that it's not reasonable to somehow have some unified test running experience that lets run tests and handle retries (or their configuration) in a similar fashion for VMTest and HWTest?

Comment 3 by ihf@chromium.org, Jul 26 2017

Cc: ihf@chromium.org
The problem there wasn't a failing test, but that the VM disappeared and couldn't be connected to anymore. What is needed here is a pool of VMs (to run tests in parallel on the server) and VM recovery.

Comment 4 by pwang@chromium.org, Aug 10 2017

Cc: pwang@chromium.org

Comment 5 by akes...@chromium.org, Aug 18 2017

Mergedinto: 750918
Status: Duplicate (was: Available)
►

Sign in to add a comment