ostestr --no-discover does not create subunit file

Bug #1597111 reported by Luz Cazares
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
os-testr
Undecided
Luz Cazares

Bug Description

Having os-testr V.0.7.0 installed
When using ostestr with --no-discover option. TCs are successfully run but results file under .testrepository is not created.
Underneath ostestr, it is running command: "python -m subunit.run" instead of "testr run.

In order to keep consistency with testr, the expectation would be to store resulting subunit file unser .testrepository. This is writing the output to disk and pass it to stdout or subunit-trace at the same time.

Changed in os-testr:
status: New → Confirmed
assignee: nobody → Luz Cazares (luz-cazares)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-testr (master)

Fix proposed to branch: master
Review: https://review.openstack.org/339189

Changed in os-testr:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-testr (master)

Reviewed: https://review.openstack.org/339189
Committed: https://git.openstack.org/cgit/openstack/os-testr/commit/?id=054fb04f669d1edffce54fdb58d3dad17fae0a6d
Submitter: Jenkins
Branch: master

commit 054fb04f669d1edffce54fdb58d3dad17fae0a6d
Author: Luz Cazares <email address hidden>
Date: Thu Jul 7 11:51:46 2016 -0700

    Save subunit results file when using --no-discover

    When using ostestr --no-discover flag. The output subunit
    results file is not saved under .testrepository as it is
    when using testr run command.

    Change-Id: Ied6c5a46661b3b36bf15fd538bc6cac764fddcc8
    Closes-Bug: #1597111

Changed in os-testr:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions