On 06/18/2013 12:49 PM, Jay Pipes wrote:
On 06/18/2013 12:43 PM, Martina Kollarova wrote:
Jenkins keeps running all the tests, even if the basic pep8 test fails,
and runs all of the (very slow) Tempest Quantum tests, even though
almost all of them are failing.
I propose that it should fail and stop all of the other tests once there
is a failure in a voting test. For non-voting tests, it should stop only
itself, not the others.
This would decrease the feedback loop and we wouldn't have to wait for
the non-voting Quantum tests to see that they failed as always.
The nosetest tool has a parameter '--stop' which will cause it to exit
on first failure.
++ I support this on the check pipeline. It may certainly reduce the
time that folks are waiting on checks...
First, by the time we get to H2, nose will probably not be running
tempest in the gate, so any nose specific options are off the table.
Secondly, getting all the results on a fail is typically really useful.
Given that this is a non interactive environment, the only way you have
to get to the bottom of the issue is to look at the logs. If we don't
run some of the tests because we stop early, that really reduces your
ability to debug the issue.
-Sean
--
Sean Dague
http://dague.net
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
