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/check/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/check/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/check/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? > > 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). > > 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