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

Issue 820076 link

Starred by 1 user
Status: Unconfirmed
Owner: ----
Cc:
akes...@chromium.org
█ jkop@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature



Sign in to add a comment

Some failures corrupt the DUT to a state which cannot pass any tests until reboot.

Reported by kasaiahx...@intel.com, Mar 8 2018 
UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36

Steps to reproduce the problem:
In some cases, we will be seeing intermittent failures during automation and these failures will get resolved after reboot the DUT. Fix is added for the same

What is the expected behavior?
Current fix will retry the job if the test fails.

What went wrong?
We had a feature to retry the job but not reboot and retry. So, we have added this feature in current fix.

Did this work before? N/A 

Chrome version:   Channel: n/a
OS Version: 
Flash Version:

Comment 1 by jkop@chromium.org, Mar 15 2018

Cc: akes...@chromium.org jkop@chromium.org
Components: Infra>Client>ChromeOS
Labels: -Pri-2 Needs-Investigation Pri-3
Summary: Some failures corrupt the DUT to a state which cannot pass any tests until reboot. (was: Add --reboot-on-retry to autotest test_that)
Your approach in crrev.com/c/956783/8 is unworkable. It relies on properties the system does not have and is either nonfunctional or extraordinarily time-consuming.

A good solution would check what properties of the failure make the reboot necessary.

A good approach to the bug would reproduce the error and narrow down what cases could cause it, instead of trying to fix something poorly understood.
►

Sign in to add a comment