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.
-1
In addition to the other objections, we currently get a lot of false
positives (fail, retry, fail, retry, succeed), and it would be harder to
debug these problems if the output was truncated differently each time.
Is anyone working on fixing the perma-failing Quantum test? When the
Postgres test was perma-failing, one of the infrastructure folks gave us
an ultimatum that if nobody fixed it soon, it would be disabled. (Happy
ending: Mauro fixed it before it got disabled.)
--
David Ripton Red Hat drip...@redhat.com
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
