I just verified, Thanks a lot.


From: Kevin Benton <<>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
Date: Friday, August 15, 2014 at 4:56 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
Subject: Re: [openstack-dev] [neutron] [third-party] What tests are required to 
be run

You didn't wait long enough for the Big Switch CI to reach your negative test. 
 Currently the CI system is backed by about 100 patches to push responses out 
~22 hours.

This does bring up an old discussion that was never resolved.
What is the minimum expected response time for CI systems?

On Fri, Aug 15, 2014 at 3:35 PM, Edgar Magana 
<<>> 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!

On 8/14/14, 8:30 AM, "Kyle Mestery" 
<<>> wrote:

>Folks, I'm not sure if all CI accounts are running sufficient tests.
>Per the requirements wiki page here [1], everyone needs to be running
>more than just Tempest API tests, which I still see most neutron
>third-party CI setups doing. I'd like to ask everyone who operates a
>third-party CI account for Neutron to please look at the link below
>and make sure you are running appropriate tests. If you have
>questions, the weekly third-party meeting [2] is a great place to ask
>OpenStack-dev mailing list

OpenStack-dev mailing list<>

Kevin Benton
OpenStack-dev mailing list

Reply via email to