refstack-client - Inconsistency between test list supplied in argument to test list executed

Bug #1633636 reported by David Paterson
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
refstack
Fix Released
High
Unassigned

Bug Description

Something seems wrong with how refstack-client is building the list of tests to run.

I passed in a file with 222 tests but it looks like 791 tests were run.

Command Run
===================================================
./refstack-client test -c tempest.conf -v --test-list "/home/stack/refstack-client/test_cases.txt"

Output
==================================================
2016-10-14 16:15:20,312 refstack_client.list_parser:139 DEBUG Number of tests: 222
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-500} \
OS_TEST_LOCK_PATH=${OS_TEST_LOCK_PATH:-${TMPDIR:-'/tmp'}} \
${PYTHON:-python} -m subunit.run discover -t ${OS_TOP_LEVEL:-./} ${OS_TEST_PATH:-./tempest/test_discover} --load-list /tmp/tmpeCEgLb
....
======
Totals
======
Ran: 791 tests in 7479.0000 sec.

=================================
Why 791 tests run instead of 222?

Attached is file containing both lists, test_cases.txt and the contents of /tmp/tmpeCEgLb which was passed to subunit.

Revision history for this message
David Paterson (davpat2112) wrote :
Revision history for this message
Catherine Diep (cdiep) wrote :

Hi David,
There was a bug in RefStack that used IDs instead of fully qualified test names to generate the whitelist used by ostestr. This patch [1] fixes that. Could you please check to see whether this will help! Thanks a lot!

[1] https://review.openstack.org/#/c/381232/

Revision history for this message
Catherine Diep (cdiep) wrote :
Changed in refstack:
status: New → Fix Committed
Catherine Diep (cdiep)
Changed in refstack:
importance: Undecided → Critical
importance: Critical → High
Martin Kopec (mkopec)
Changed in refstack:
status: Fix Committed → Fix Released
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.