add ability to dry-run a parallel job

Bug #1273912 reported by Leah Klearman on 2014-01-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Testrepository
Wishlist
Unassigned

Bug Description

if you're trying to troubleshoot your group_regex, you shouldn't have to run the whole job and then pick apart the results filtering by worker in order to figure out if the regex did the right thing. maybe allow for the combination of --parallel and --list ?

Robert Collins (lifeless) wrote :

I'm not quite sure what the UI should be, but clearly this is an important use case.

Changed in testrepository:
status: New → Triaged
importance: Undecided → Wishlist
Robert Collins (lifeless) wrote :

Just making some notes for anyone who wants to do this:

 - need to preserve the existing command (test enumeration is needed)
 - shouldn't depend on re-invoking - we may want a command interface in future for online scheduling,so this should be explicitly handled in testr
 - dry-run is rougly equivalent to --list-tests, in that that also enumerates and doesn't run, so --list-tests --parallel could perhaps be a way forward
 - another way would be to enumerate and schedule, and output via subunit with worker tags

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

Other bug subscribers