From: Ivar Lazzaro >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" >
Date: Friday, August 15, 2014 at 3:47 PM
To: "OpenStack Development Mailing List (not for usage questions)" >
Subject: Re: [openstack-dev] [neutron] [third-party] What tests are required to be run
Nice shot, to be the inquisitor is not necessarily a bad thing :)
I know some CIs are 'stuck' waiting for bugs to be fixed or certain patches to be merged, but I was wondering if it is a requirement that CIs vote ALL the Neutron patches. Some may have missed your call just because of their filters (see  section 'what changes to run against').
On Sat, Aug 16, 2014 at 12:35 AM, Edgar Magana <edgar.magana at workday.com<mailto:edgar.magana at workday.com>> wrote:
I did a quick audit on the Neutron CI. Very sad results. Only few plugins
and drivers are running properly and testing all Neutron commits.
I created a report here:
We will discuss the actions to take on the next Neutron IRC meeting. So
please, reach me out to clarify what is the status of your CI.
I had two commits to quickly verify the CI reliability:
I would expect all plugins and drivers passing on the first one and
failing for the second but I got so many surprises.
Neutron code quality and reliability is a top priority, if you ignore this
report that plugin/driver will be candidate to be remove from Neutron tree.
P.s. I hate to be the inquisitor here? but someone has to do the dirty job!