"run.py: error: no such option: -t" when running tests

Bug #1223522 reported by Robert Collins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-troveclient
Confirmed
Medium
Unassigned

Bug Description

Reported via https://bugs.launchpad.net/ubuntu/+source/python-troveclient/+bug/1223097
->
https://jenkins.openstack.org/view/All/job/gate-python-troveclient-python27/52/console
->2013-08-06 04:27:53.276 | py27 runtests: commands[0] | python setup.py testr --testr-args=
2013-08-06 04:27:53.800 | running testr
2013-08-06 04:27:54.432 | Usage: run.py [options] <cmd> <action> <args>
2013-08-06 04:27:54.432 |
2013-08-06 04:27:54.433 | run.py: error: no such option: -t

(continues below)

From memory this is printing this out because 'run.py' is the python file for 'subunit.run', the runner in use, it's 'harmless' stipple from tests/code discovery, but it's super confusing for people seeing it.

2013-08-06 04:27:54.435 | Usage: run.py [options] <cmd> <action> <args>
2013-08-06 04:27:54.435 |
2013-08-06 04:27:54.435 | run.py: error: no such option: -t
2013-08-06 04:27:54.446 | Usage: run.py [options] <cmd> <action> <args>
2013-08-06 04:27:54.446 |
2013-08-06 04:27:54.446 | run.py: error: no such option: -t
2013-08-06 04:27:54.451 | Usage: run.py [options] <cmd> <action> <args>
2013-08-06 04:27:54.452 |
2013-08-06 04:27:54.452 | run.py: error: no such option: -t
2013-08-06 04:27:54.475 | Usage: run.py [options] <cmd> <action> <args>
2013-08-06 04:27:54.475 |
2013-08-06 04:27:54.476 | run.py: error: no such option: -t
2013-08-06 04:27:54.477 | Usage: run.py [options] <cmd> <action> <args>
2013-08-06 04:27:54.477 |
2013-08-06 04:27:54.477 | run.py: error: no such option: -t
2013-08-06 04:27:54.491 | Usage: run.py [options] <cmd> <action> <args>
2013-08-06 04:27:54.491 |
2013-08-06 04:27:54.492 | run.py: error: no such option: -t
2013-08-06 04:27:54.495 | Usage: run.py [options] <cmd> <action> <args>
2013-08-06 04:27:54.495 |
2013-08-06 04:27:54.495 | run.py: error: no such option: -t
2013-08-06 04:27:54.499 | Usage: run.py [options] <cmd> <action> <args>
2013-08-06 04:27:54.500 |
2013-08-06 04:27:54.500 | run.py: error: no such option: -t
2013-08-06 04:27:54.505 | Usage: run.py [options] <cmd> <action> <args>
2013-08-06 04:27:54.505 |
2013-08-06 04:27:54.505 | run.py: error: no such option: -t
2013-08-06 04:27:54.508 | Usage: run.py [options] <cmd> <action> <args>
2013-08-06 04:27:54.509 |
2013-08-06 04:27:54.509 | run.py: error: no such option: -t
2013-08-06 04:27:54.517 | Usage: run.py [options] <cmd> <action> <args>
2013-08-06 04:27:54.517 |
2013-08-06 04:27:54.518 | run.py: error: no such option: -t
2013-08-06 04:27:54.519 | Usage: run.py [options] <cmd> <action> <args>
2013-08-06 04:27:54.520 |
2013-08-06 04:27:54.520 | run.py: error: no such option: -t
2013-08-06 04:27:54.521 | Usage: run.py [options]
2013-08-06 04:27:54.522 |
2013-08-06 04:27:54.522 | run.py: error: no such option: -t
2013-08-06 04:27:54.526 | Usage: run.py [options] <cmd> <action> <args>
2013-08-06 04:27:54.526 |
2013-08-06 04:27:54.526 | run.py: error: no such option: -t
2013-08-06 04:27:54.907 | running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
2013-08-06 04:27:54.907 | OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
2013-08-06 04:27:54.908 | OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-60} \
2013-08-06 04:27:54.908 | ${PYTHON:-python} -m subunit.run discover -t ./ ./troveclient/tests --list
2013-08-06 04:27:54.908 | running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
2013-08-06 04:27:54.908 | OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
2013-08-06 04:27:54.908 | OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-60} \
2013-08-06 04:27:54.908 | ${PYTHON:-python} -m subunit.run discover -t ./ ./troveclient/tests --load-list /tmp/tmp.65k5NWuK2h/tmp6eNUWX
2013-08-06 04:27:54.908 | running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
2013-08-06 04:27:54.908 | OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
2013-08-06 04:27:54.908 | OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-60} \
2013-08-06 04:27:54.908 | ${PYTHON:-python} -m subunit.run discover -t ./ ./troveclient/tests --load-list /tmp/tmp.65k5NWuK2h/tmpAU351d
2013-08-06 04:27:54.908 | running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
2013-08-06 04:27:54.908 | OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
2013-08-06 04:27:54.908 | OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-60} \
2013-08-06 04:27:54.908 | ${PYTHON:-python} -m subunit.run discover -t ./ ./troveclient/tests --load-list /tmp/tmp.65k5NWuK2h/tmpP7Wx41
2013-08-06 04:27:54.908 | running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
2013-08-06 04:27:54.909 | OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
2013-08-06 04:27:54.909 | OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-60} \
2013-08-06 04:27:54.909 | ${PYTHON:-python} -m subunit.run discover -t ./ ./troveclient/tests --load-list /tmp/tmp.65k5NWuK2h/tmpKT1fUM
2013-08-06 04:27:54.909 | Ran 326 tests in 0.325s

Changed in python-troveclient:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Sushil Kumar (sushil-kumar2) wrote :

The source bug says that, Fix committed and Fix Released, wondered, if this is still a bug anymore in the system

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.