[openstack-dev] [neutron] [third-party] What tests are required to be run
Edgar Magana
edgar.magana at workday.com
Fri Aug 22 17:56:33 UTC 2014
Excellent Job!
Thanks a lot, I have updated the wiki.
Edgar
From: Hemanth Ravi <hemanthraviml at gmail.com<mailto:hemanthraviml at gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Thursday, August 21, 2014 at 1:37 PM
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] [neutron] [third-party] What tests are required to be run
Edgar,
CI name: One Convergence CI
The logs issue has been fixed and earlier tests were failing due to https://review.openstack.org/#/c/114146
For reference:
1. Please take a look at the vote on patchset 7 in https://review.openstack.org/#/c/114968/
2. Logs at https://www.dropbox.com/sh/czydzz5bn2rc2lp/AABZByV8UQUIqWaZSSrZvzvDa
Thanks,
-hemanth
On Thu, Aug 21, 2014 at 12:41 PM, Kevin Benton <blak111 at gmail.com<mailto:blak111 at gmail.com>> wrote:
Our system would get backed up with patches and sometimes take up to 10 hours to respond with results for a change.
We should establish some maximum acceptable time to get the results for a patch.
On Thu, Aug 21, 2014 at 11:59 AM, Edgar Magana <edgar.magana at workday.com<mailto:edgar.magana at workday.com>> wrote:
Maximum time to vote, can you clarify?
Edgar
From: Kevin Benton <blak111 at gmail.com<mailto:blak111 at gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Tuesday, August 19, 2014 at 1:11 PM
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] [neutron] [third-party] What tests are required to be run
I also added a two more nodes to our cluster to reduce the delay. Can we establish a maximum time to vote on the wiki?
On Aug 19, 2014 9:39 AM, "Edgar Magana" <edgar.magana at workday.com<mailto:edgar.magana at workday.com>> wrote:
Kevin,
I just verified, Thanks a lot.
Edgar
From: Kevin Benton <blak111 at gmail.com<mailto:blak111 at gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Friday, August 15, 2014 at 4:56 PM
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
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 <edgar.magana at workday.com<mailto:edgar.magana at workday.com>> wrote:
Team,
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:
https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers#Existing_Plugin
_and_Drivers
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:
https://review.openstack.org/#/c/114393/
https://review.openstack.org/#/c/40296/
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.
Cheers,
Edgar
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" <mestery at mestery.com<mailto:mestery at mestery.com>> 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
>questions.
>
>Thanks,
>Kyle
>
>[1] https://wiki.openstack.org/wiki/NeutronThirdPartyTesting
>[2] https://wiki.openstack.org/wiki/Meetings/ThirdParty
>
>_______________________________________________
>OpenStack-dev mailing list
>OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Kevin Benton
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Kevin Benton
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140822/2399539d/attachment.html>
More information about the OpenStack-dev
mailing list