From 40908f6f4fde6642637dc2b0269daf78d47b3844 Mon Sep 17 00:00:00 2001 From: Chris Chen Date: Fri, 22 Jul 2016 11:20:45 -0700 Subject: cts: Added corruption detection If test suite doesn't finish or results are received out of order, this is likely an indication of reset or hang by one of the boards and all tests after the point of corruption are marked as corrupted. BRANCH=None BUG=None TEST=Manual - Edit the gpio th code to change ordering of tests or hang or reset, etc. - Build and flash tests - Run './cts/cts.py -r' - You should see the results for all of the tests, with all corrupted tests marked as corrupted Change-Id: I7925e37db285a4e90e6e09bf3b187400ddfe9edf Reviewed-on: https://chromium-review.googlesource.com/362614 Commit-Ready: Chris Chen Tested-by: Chris Chen Reviewed-by: Randall Spangler --- cts/gpio/cts.testlist | 2 ++ 1 file changed, 2 insertions(+) (limited to 'cts/gpio') diff --git a/cts/gpio/cts.testlist b/cts/gpio/cts.testlist index 8a6656db1d..e59be1c7ce 100644 --- a/cts/gpio/cts.testlist +++ b/cts/gpio/cts.testlist @@ -3,6 +3,8 @@ * found in the LICENSE file. */ +/* Currently tests will execute in the order they are listed here */ + /* Test whether sync completes successfully */ CTS_TEST(sync_test) /* Check if the dut can set a line low */ -- cgit v1.2.1