tempest - non-zero exit code (2) from test listing

Bug #1396679 reported by Ryan Beisner
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Charm Testing
Invalid
Undecided
Ryan Beisner
ubuntu-openstack-ci
Invalid
Undecided
Ryan Beisner

Bug Description

tempest runs 0 tests due to listing error; it is likely that the tempest template needs to be updated and cross-checked against the new and deprecated options.

Non-zero exit code (2) from test listing. stdout='\xb3 `{\xe4\x17text/plain;charset=utf8\rimport errors{\xb3tempest.api.baremetal.admin.test_api_discovery\ntempest.api.baremetal.admin.test_chassis\ntempest.api.baremetal.admin.test_drivers\ntempest.api.baremetal.admin.test_nodes\ntempest.api.baremetal.admin.test_nodestates\ntempest.api.bar
...

Ran 0 tests in 1.786s

OK

Ryan Beisner (1chb1n)
tags: added: openstack uosci
Revision history for this message
Ryan Beisner (1chb1n) wrote :

template directives were fine; ended up being a dependency issue. resolved via tempest's requirements.txt.

Changed in openstack-charm-testing:
assignee: nobody → Ryan Beisner (1chb1n)
Changed in ubuntu-openstack-ci:
assignee: nobody → Ryan Beisner (1chb1n)
Changed in openstack-charm-testing:
status: New → Invalid
Changed in ubuntu-openstack-ci:
status: New → Invalid
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.