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

Issue 632097 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

autotest sequence-based suites can't be run from test_that

Project Member Reported by tbroch@chromium.org, Jul 27 2016

Issue description

test_that <dut> power_daily

INFO:root:Identity added: /tmp/test_that_results_VXAqb3/testing_rsa (/tmp/test_that_results_VXAqb3/testing_rsa)
INFO:root:Board unspecified, attempting to determine board from host.
INFO:root:Starting master ssh connection '/usr/bin/ssh -a -x -N -o ControlMaster=yes -o ControlPath=/tmp/_autotmp_E_Qm9Jssh-master/socket -o StrictHostKeyChecking=no -o UserKnownHostsFile=/tmp/tmpBBBNfh -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=300 -l root -p 22 chromeos1-row2-rack9-host4.cros'
INFO:root:Starting master ssh connection '/usr/bin/ssh -a -x   -N -o ControlMaster=yes -o ControlPath=/tmp/_autotmp_OpyHhwssh-master/socket -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=900 -o ServerAliveCountMax=3 -o ConnectionAttempts=4 -o Protocol=2 -l root -p 22 chromeos1-row2-rack9-host4.cros'
INFO:root:Detected host board: cyan
12:08:17 INFO | Began logging to /tmp/test_that_results_VXAqb3
Adding labels [u'cros-version:ad_hoc_build', u'board:cyan'] to host chromeos1-row2-rack9-host4.cros
14:08:17 INFO | Fetching suite for job named power_daily...
14:08:19 ERROR| No test found, searching for possible tests with job name similar to power_daily
Traceback (most recent call last):
  File "/mnt/host/source/src/third_party/autotest/files/site_utils/test_that.py", line 347, in <module>
    sys.exit(main(sys.argv[1:]))
  File "/mnt/host/source/src/third_party/autotest/files/site_utils/test_that.py", line 343, in main
    return _main_for_local_run(argv, arguments)
  File "/mnt/host/source/src/third_party/autotest/files/site_utils/test_that.py", line 300, in _main_for_local_run
    pretend=arguments.pretend)
  File "/mnt/host/source/src/third_party/autotest/files/site_utils/test_runner_utils.py", line 679, in perform_run_from_autotest_root
    host_attributes=host_attributes)
  File "/mnt/host/source/src/third_party/autotest/files/site_utils/test_runner_utils.py", line 510, in perform_local_run
    ignore_deps=ignore_deps)
  File "/mnt/host/source/src/third_party/autotest/files/site_utils/test_runner_utils.py", line 161, in fetch_local_suite
    'following tests?\n  %s' % '\n  '.join(possible_tests))
ValueError: Found no tests. Check your suite name, test name, or test matching wildcard.
Did you mean any of following tests?
  power_Idle
  power_Thermal
  power_Standby
  power_CPUIdle
  power_Draw
  Power daily tests
  power_Backlight
  power_Status
  power_DarkResumeDisplay
  power_IdleSuspend

Likely an expected outcome.  Curious if there's a plan to support these suite types w/in test_that?
 
Components: Infra>Client>ChromeOS
Components: -Infra>Client>ChromeOS Test

Sign in to add a comment