The root cause for the issue was the fact that our devstack VMs were still running libvirt 0.9.8 and we missed the commit where libvirt 0.9.11 was forced as a minimum requirement.
This has been fixed for a while now. However, I made a mistake and as a result some patches have received a -1 from VMware mine sweeper about half an hour after the CI system upvoted the same patch. This has been rectified as well now. My apologies to all the developers affected. Salvatore On 31 July 2014 02:19, Paddu Krishnan (padkrish) <[email protected]> wrote: > I am still hitting this issue. Are the infrastructure related failures > white-listed? > > Thanks, > Paddu > > From: Joe Gordon <[email protected]> > Reply-To: "OpenStack Development Mailing List (not for usage questions)" < > [email protected]> > Date: Wednesday, July 30, 2014 4:18 PM > To: OpenStack Development Mailing List <[email protected]> > Subject: Re: [openstack-dev] [Neutron][CI] VMware mine sweeper for > Neutron temporarily disabled > > > On Jul 29, 2014 12:46 PM, "Salvatore Orlando" <[email protected]> wrote: > > > > Minesweeper for Neutron is now running again. > > We updated the image for our compute nodes to ensure it is compliant > with commit [1]. > > Does this mean you had libvirt < 0.9.11 in minesweeper? I am wondering if > others will hit the issue (and maybe we revert the minimum) or not. > > > > > We are still observing occasional infrastructure-related issues > manifesting as request timeout failures. We will soon whitelist those > failures so that mine sweeper won't vote when they're hit. > > > > Regards, > > Salvatore > > > > [1] > https://github.com/openstack/nova/commit/842b2abfe76dede55b3b61ebaad5a90c356c5ace > > > > > > > > > > On 28 July 2014 13:07, Salvatore Orlando <[email protected]> wrote: > >> > >> Hi, > >> > >> We have been witnessing some issues in our infrastructure which > resulted in Mine Sweeper test run failures. Unfortunately these failures > resulted in -1s being put on several patches. > >> > >> Mine sweeper is now temporarily disabled and our team is already > working on solving the issue. > >> In the meanwhile, you can trigger a recheck with "recheck-vmware" to > remove the negative score from your patch. > >> > >> Salvatore > > > > > > > > _______________________________________________ > > OpenStack-dev mailing list > > [email protected] > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
