Open Stack

On 2013-06-18 18:43:58 +0200 (+0200), Martina Kollarova wrote:
[...]
> 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.
[...]

We did this for a while (ran pep8 first in the check pipeline, then
ran other jobs if that passed), but it turned out to have a rather
confusing interaction with the requirements validation jobs.

The long and short of it is that there are roughly two classes of
jobs we want to consider... quick ones which are not very resource
intensive, and more involved tests which are unlikely to succeed
anyway if the quick ones fail. To that end there has been discussion
of adding a "fast-fail" option for certain jobs causing them to
abort others already running and return the result set right away so
that developers can benefit from a more immediate testing feedback
loop.

I don't think we have a timeline for implementation there, but it's
my recollection that's the direction we resolved to take it.
-- 
Jeremy Stanley