hardware_StorageWearoutDetect: move to bvt-perbuild.
This is a good test. The problem is it detects hardware health of
an individual DUT. By the time the DUT is replaced random machine
allocation causes flakes. For this reason it can't be in bvt-cq.
BUG=chromium:589344
TEST=https://wmatrix.googleplex.com/bvt-cq
hardware_StorageWearoutDetect View test details and logs for hardware_StorageWearoutDetect.
R53-8458.0.0
R53-8460.0.0
R53-8462.0.0
R53-8462.0.0-rc2
R53-8463.0.0-rc2
R53-8479.0.0
R53-8484.0.0
R53-8485.0.0
R53-8486.0.0
R53-8491.0.0
R53-8500.0.0
R53-8502.0.0
R53-8504.0.0
R53-8506.0.0
R53-8510.0.0
celes
edgar
expresso
peach_pit
veyron_jaq
veyron_mighty
winky
Detected wearout parameter:MMC failure DEVICE_LIFE_TIME_EST_TYP_A
Detected wearout parameter:MMC failure DEVICE_LIFE_TIME_EST_TYP_B
Detected wearout parameter:MMC failure DEVICE_LIFE_TIME_EST_TYP_BMMC failure DEVICE_LIFE_TIME_EST_TYP_A
FAIL bvt-cq Mon Jun 27, 22:52 ...
Change-Id: I57ac64f6ead54541e3948f3b88604e2494ba54d3
Reviewed-on: https://chromium-review.googlesource.com/356581
Reviewed-by: Ilja H. Friedel <ihf@chromium.org>
Tested-by: Ilja H. Friedel <ihf@chromium.org>
diff --git a/client/site_tests/hardware_StorageWearoutDetect/control b/client/site_tests/hardware_StorageWearoutDetect/control
index fbf3ade..7fe05bb 100644
--- a/client/site_tests/hardware_StorageWearoutDetect/control
+++ b/client/site_tests/hardware_StorageWearoutDetect/control
@@ -8,7 +8,11 @@
TIME = 'FAST'
TEST_CLASS = 'hardware'
TEST_TYPE = 'client'
-ATTRIBUTES = "suite:bvt-cq"
+# This test measures the hardware health of individual DUTs. If it fails the DUT
+# needs to be replaced. This test should not run in bvt-cq which will cause
+# flakes due to random machine allocation when a DUT nears end of life (and slow
+# bug filing/DUT replacement in lab).
+ATTRIBUTES = "suite:bvt-perbuild"
JOB_RETRIES = 2
DOC = """