mark setup stage success/skip
With how we currently handle things, the easiest way to enforce a different reporter-ng behavior on some stage success/failure, is to manually and properly mark if the stage failed or passed. Weird infrastructure issues happening in the middle of the stage will never get to to "stage passed" code.
Signed-off-by: Jakub Racek jracek@redhat.com