I'm not sure if this is possible with a Zuul setup, but once we identify a
failure causing commit, we change the reported job status to (skipped)
for any patches that contain the commit but not the fix. It's a relatively
straightforward way to communicate that the CI system is still operational
and the tools just seem to be at odds in this situation.
From: Kevin Benton [mailto:blak...@gmail.com]
Sent: Thursday, August 21, 2014 3:25 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] How to handle blocking bugs/changes in
Neutron 3rd
Preface: I posed this problem on the #openstack-infra IRC, and they couldn't
offer an easy or obvious solution, and suggested that I get some consensus from
the Neutron community as to how we want to handle this situation. So I'd like
to bounce this around, get some ideas, and maybe bring this
