cheets tests failure: Could not find any tests in module |
||||||||
Issue descriptionExample build: https://luci-milo.appspot.com/buildbot/chromeos/kevin-paladin/1052 Affected tests: cheets_CTS_N.CtsAccountManagerTestCases cheets_CTS_N.CtsDramTestCases cheets_CTS_N.CtsOpenGLTestCases cheets_CTS_N.CtsOpenGlPerf2TestCases Log snippet: 05/11 12:06:36.928 WARNI| test:0615| The test failed with the following exception Traceback (most recent call last): File "/usr/local/autotest/client/common_lib/test.py", line 609, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/usr/local/autotest/client/common_lib/test.py", line 817, in _call_test_function return func(*args, **dargs) File "/usr/local/autotest/client/common_lib/test.py", line 470, in execute dargs) File "/usr/local/autotest/client/common_lib/test.py", line 347, in _call_run_once_with_retry postprocess_profiled_run, args, dargs) File "/usr/local/autotest/client/common_lib/test.py", line 380, in _call_run_once self.run_once(*args, **dargs) File "/usr/local/autotest/server/site_tests/cheets_CTS_N/cheets_CTS_N.py", line 372, in run_once raise error.TestFail('Error: Could not find any tests in module.') TestFail: Error: Could not find any tests in module.
,
May 11 2017
Can the sheriffs take a quick look?
,
May 11 2017
,
May 11 2017
That means CTS is dead.
,
May 11 2017
,
May 11 2017
It is a bit strange, but my only candidate for these failures is https://chromium-review.googlesource.com/#/c/500238/ but it did not show CTS failures in earlier HWTest runs. Xixuan, could it be that because of the self-exploding CQ failures were not encountered in earlier runs of HWTest?
,
May 11 2017
it's possible. The CL breaks https://luci-milo.appspot.com/buildbot/chromeos/link-paladin/28281, which is part of master-paladin https://luci-milo.appspot.com/buildbot/chromeos/master-paladin/14546, where kevin-paladin is still running HWTest, not finished.
,
May 11 2017
Hmm? All the code changed in the CL should not even executed at all for the CTS tests. (The CL only changes the behavior of ext4-migration but CTS always uses newly created profile.) If the CL really affects the tests, there's something seriously wrong in somewhere else... I rather suspect some other CL in the same CQ. I'll take a closer look soon (in 1.5 hour)
,
May 11 2017
The only other candidate would be https://chromium-review.googlesource.com/#/c/472908/
,
May 12 2017
A log from https://luci-milo.appspot.com/buildbot/chromeos/kevin-paladin/1049 (which, by the way does not include my CL): https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/116897732-chromeos-test/chromeos2-row8-rack8-host4/debug/ 05/11 04:05:09.723 DEBUG| utils:0297| [stdout] 05-11 04:05:09 E/ApkPreconditionCheck: Target preparation step testExternalStoragePresent failed. 05/11 04:05:09.724 DEBUG| utils:0297| [stdout] junit.framework.AssertionFailedError: Device must have external storage mounted in order to run CTS 05/11 04:05:09.724 DEBUG| utils:0297| [stdout] at junit.framework.Assert.fail(Assert.java:50) 05/11 04:05:09.724 DEBUG| utils:0297| [stdout] at junit.framework.Assert.assertTrue(Assert.java:20) 05/11 04:05:09.724 DEBUG| utils:0297| [stdout] at com.android.preconditions.cts.PreconditionsTest.testExternalStoragePresent(PreconditionsTest.java:54) so yes that might be filesystem related.
,
May 17 2017
So this was about a change in CQ.
,
May 23 2017
,
Mar 31 2018
Bulk closing old unconfirmed issues. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by ayatane@chromium.org
, May 11 2017