Zuul has a feature that makes it possible to only run some jobs after others have passed:
https://zuul-ci.org/docs/zuul/user/config.html#attr-job.dependencies
Except for tempest and grenade (which take about an hour to 1.5 hours to run, sometimes a lot more) the usual time for any of the placement tests is less than 6 minutes each, sometimes less than 4.
I've been wondering if we might want to consider only running tempest and grenade if the other tests have passed first? So here's this message seeking opinions.
On the one hand this ought to be redundant. The expectation is that a submitter has already done at least one python version worth of unit and functional tests. Fast8 too. On one of my machines 'tox -efunctional-py37,py37,pep8' on warmed up virtualenvs is a bit under 53 seconds. So it's not like it's a huge burden or cpu melting.
But on the other hand, if someone has failed to do that, and they have failing tests, they shouldn't get the pleasure of wasting a tempest or grenade node.
Another argument I've heard for not doing this is if there are failures of different types in different tests, having all that info for the round of fixing that will be required is good. That is, getting a unit failure, fixing that, then subumitting again, only to get an integration failure which then needs another round of fixing (and testing) might be rather annoying.
I'd argue that that's important information about unit or functional tests being insufficient.
I'm not at all sold on the idea, but thought it worth "socializing" for input.
Thanks.