[ovirt-devel] oVirt CI now supports Fedora 27 and Fedora Rawhide

[Barak Korren]

On 23 November 2017 at 09:27, Francesco Romani <fromani at redhat.com> wrote:
>
> On 11/23/2017 08:25 AM, Barak Korren wrote:
>
>
> The package exists:
> http://resources.ovirt.org/repos/ovirt/tested/master/rpm/fc27/noarch/ovirt-imageio-common-1.2.0-0.201711212128.git9926984.fc27.noarch.rpm
>
> repoquery is happy:
> $ repoquery
> --repofrompath=r,http://resources.ovirt.org/repos/ovirt/tested/master/rpm/fc27
> --repoid=r list ovirt-imageio-common
> ovirt-imageio-common-0:1.2.0-0.201711212128.git9926984.fc27.noarch
>
> Maybe mock caching issue?
>
> 00:00:28.127 Using chroot cache =
> /var/cache/mock/fedora-27-x86_64-a9934b467f29c7317f7dd8f205d66ddd
> 00:00:28.127 Using chroot dir =
> /var/lib/mock/fedora-27-x86_64-a9934b467f29c7317f7dd8f205d66ddd-7425
>
>
> No. This just tells you where the cache would be, not if its actually
> there already.
> But yeah, this run actually did use a cached chroot:
>
>      00:00:28.767 Start: unpacking root cache
>      00:01:01.624 Finish: unpacking root cache
>
> I cleaned it from the node and retriggerd, lets see what happens now:
>
>
> http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc27-x86_64/85/console
>
> Failed again:
>
>     00:11:56.063
> -----------------------------------------------------------------------------------------------------------------------------------------
>     00:11:56.064 TOTAL
>                                                                 49960
> 25280    49%
>     00:11:56.064
> ----------------------------------------------------------------------
>     00:11:56.065 Ran 2547 tests in 307.236s
>     00:11:56.065
>     00:11:56.065 FAILED (SKIP=78, failures=4)
>     00:11:56.065 make[1]: *** [Makefile:1118: check] Error 1
>     00:11:56.066 make[1]: Leaving directory
> '/home/jenkins/workspace/vdsm_master_check-patch-fc27-x86_64/vdsm/tests'
>     00:11:56.066 ERROR: InvocationError: '/usr/bin/make -C tests check'
>     00:11:56.067 storage-py27 create:
> /home/jenkins/workspace/vdsm_master_check-patch-fc27-x86_64/vdsm/.tox/storage-py27
>     00:11:59.803 storage-py27 installdeps: pytest==3.1.2, nose==1.3.7
>
> ....
>
>     00:14:06.238 ___________________________________ summary
> ____________________________________
>     00:14:06.238 ERROR:   tests: commands failed
>     00:14:06.238   storage-py27: commands succeeded
>     00:14:06.238 SKIPPED:  storage-py35: InterpreterNotFound: python3.5
>     00:14:06.239   storage-py36: commands succeeded
>     00:14:06.239   lib-py27: commands succeeded
>     00:14:06.264 make: *** [Makefile:1019: tests] Error 1
>     00:14:06.270 + collect-logs
>     00:14:06.270 + cp /var/log/vdsm_tests.log
> /home/jenkins/workspace/vdsm_master_check-patch-fc27-x86_64/vdsm/exported-artifacts/
>     00:14:06.280 Took 488 seconds
>
>
> I can't really tell why this failed, also did we use to have the
> results exported to XUINT?
>
>
> It seems it failed because:
>
> 07:12:24
> 07:12:24
> ======================================================================
> 07:12:24 FAIL: test_multiple_vlans (network.tc_test.TestConfigureOutbound)
> 07:12:24
> ----------------------------------------------------------------------
> 07:12:24 Traceback (most recent call last):
> 07:12:24   File "/usr/lib/python2.7/site-packages/mock/mock.py", line 1305,
> in patched
> 07:12:24     return func(*args, **keywargs)
> 07:12:24   File
> "/home/jenkins/workspace/vdsm_master_check-patch-fc27-x86_64/vdsm/tests/network/tc_test.py",
> line 459, in test_multiple_vlans
> 07:12:24     self._analyse_qos_and_general_assertions()
> 07:12:24   File
> "/home/jenkins/workspace/vdsm_master_check-patch-fc27-x86_64/vdsm/tests/network/tc_test.py",
> line 531, in _analyse_qos_and_general_assertions
> 07:12:24     tc_filters.tagged_filters)
> 07:12:24   File
> "/home/jenkins/workspace/vdsm_master_check-patch-fc27-x86_64/vdsm/tests/network/tc_test.py",
> line 579, in _assertions_on_filters
> 07:12:24     self.assertEqual(len(untagged_filters), 1)
> 07:12:24 AssertionError: 0 != 1
> 07:12:24 -------------------- >> begin captured logging <<
> --------------------
>

Not sure what this failure means, is it something I need to fix in the infra?


-- 
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted