Open Stack

> -----Original Message-----
> From: Mikhail Medvedev [mailto:mihailmed at gmail.com]
> Sent: Monday, April 17, 2017 10:51 PM
> To: OpenStack Development Mailing List (not for usage questions)
> <openstack-dev at lists.openstack.org>
> Cc: openstack-networking-ci <openstack-networking-ci at intel.com>
> Subject: Re: [openstack-dev] [intel experimental ci] Is it actually
> checking anything?
> 
> On Mon, Apr 17, 2017 at 12:31 PM, Jay Pipes <jaypipes at gmail.com> wrote:
> > Please see the below output from the Intel Experimental CI (from
> > https://review.openstack.org/414769):
> >
> > On 04/17/2017 01:28 PM, Intel Experimental CI (Code Review) wrote:
> >>
> >> Intel Experimental CI has posted comments on this change.
> >>
> >> Change subject: placement: SRIOV PF devices as child providers
> >>
> ......................................................................
> >>
> >>
> >> Patch Set 17:
> >>
> >> Build succeeded (check pipeline).
> >>
> >> - tempest-dsvm-full-nfv-xenial
> >> http://intel-openstack-ci-logs.ovh/portland/2017-04-
> 17/414769/17/chec
> >> k/tempest-dsvm-full-nfv-xenial/1bcdb64
> >> : FAILURE in 38m 34s (non-voting)
> >> - tempest-dsvm-intel-nfv-xenial
> >> http://intel-openstack-ci-logs.ovh/portland/2017-04-
> 17/414769/17/chec
> >> k/tempest-dsvm-intel-nfv-xenial/a21d879
> >> : FAILURE in 40m 00s (non-voting)
> >> - tempest-dsvm-multinode-ovsdpdk-nfv-networking-xenial
> >> http://intel-openstack-ci-logs.ovh/portland/2017-04-
> 17/414769/17/chec
> >> k/tempest-dsvm-multinode-ovsdpdk-nfv-networking-xenial/837e59d
> >> : FAILURE in 47m 45s (non-voting)
> >
> >
> > As you can see, it says the build succeeded, but all three jobs in
> the
> > pipeline failed.
> 
> This would happen when CI is voting but all the jobs in a check are
> non-voting. Zuul ignores non-voting job result, and as there isn't a
> single voting job, it reports 'build succeeded'. Maybe it should be a
> zuul bug?
[Mooney, Sean K] yes this is the case we have all jobs currently set to non voting.
I had the same question in the past to our ci team zuuls comment is slightly non-intuitive
But form zuul point of view the job did succeed as it executed all the ci tasks and uploaded the
Results. As to what this is running we are moving the intel-nfv-ci out of our development lab
into a datacenter. The experimental ci is a duplicate of our normal intel-nfv-ci
and the intent is to swap the names and decommission our ci in our dev lab by the end of April
all going well.
> 
> >
> > Is someone actively looking into this particular 3rd party CI system?
> 
> I do not see anything wrong with that CI (apart from misleading comment
> due to zuul issue I mentioned above).
[Mooney, Sean K] it is being maintained by the same people who are maintaining the main intel-nfv-ci.
As I said above we will be swapping the main intel-nfv-ci account over to this new hardware later this month all going well.
Once we have swapped over the Intel Experimental CI account will be shut down once we decommission the infra in our dev lab. 

> 
> >
> > Best,
> > -jay
> >
> >
> ______________________________________________________________________
> > ____ OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> > OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> ---
> Mikhail Medvedev
> IBM
> 
> _______________________________________________________________________
> ___
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-
> request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev