package included in .packages file, missing in check-patch.sh - caching issue?

Description

I added 2 packages to ovirt-imageio packages files:
https://gerrit.ovirt.org/#/c/85639/

The next patch using these packages
https://gerrit.ovirt.org/#/c/85245/

fail to import the package on some slaves:

00:02:34.093 ==================================== ERRORS
====================================00:02:34.093
____________________ ERROR collecting test/qemuimg_test.py
_____________________00:02:34.093 ImportError while importing test
module '/home/jenkins/workspace/ovirt-imageio_master_check-patch-el7-x86_64/ovirt-imageio/common/test/qemuimg_test.py'.00:02:34.094
Hint: make sure your test modules/packages have valid Python
names.00:02:34.094 Traceback:00:02:34.094 test/qemuimg_test.py:16:
in <module>00:02:34.094 from ovirt_imageio_common import
qemuimg*00:02:34.094* ovirt_imageio_common/qemuimg.py:11: in
<module>00:02:34.094 from . compat import
subprocess*00:02:34.095* ovirt_imageio_common/compat.py:12: in
<module>00:02:34.095 import subprocess32 as subprocess # NOQA:
F401 (unused import)00:02:34.095 E ImportError: No module named
subprocess32*00:02:34.095* !!!!!!!!!!!!!!!!!!! Interrupted: 1 errors
during collection !!!!!!!!!!!!!!!!!!!!00:02:34.096
=========================== 1 error in 1.06 seconds
============================

Do we have a way to invalidate mock cache manually?

Nir

Activity

Show:
Nir Soffer
December 21, 2017, 4:10 PM

Forgot to add links to failing builds:
http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc25-x86_64/490/console
http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fcraw-x86_64/145/console
http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc27-x86_64/145/console
http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-el7-x86_64/769/console
http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/458/console

On Thu, Dec 21, 2017 at 5:55 PM Nir Soffer <nsoffer@redhat.com> wrote:

> I added 2 packages to ovirt-imageio packages files:
> https://gerrit.ovirt.org/#/c/85639/
>
> The next patch using these packages
> https://gerrit.ovirt.org/#/c/85245/
>
> fail to import the package on some slaves:
>
> 00:02:34.093 ==================================== ERRORS ====================================00:02:34.093 ____________________ ERROR collecting test/qemuimg_test.py _____________________00:02:34.093 ImportError while importing test module '/home/jenkins/workspace/ovirt-imageio_master_check-patch-el7-x86_64/ovirt-imageio/common/test/qemuimg_test.py'.00:02:34.094 Hint: make sure your test modules/packages have valid Python names.00:02:34.094 Traceback:00:02:34.094 test/qemuimg_test.py:16: in <module>00:02:34.094 from ovirt_imageio_common import qemuimg*00:02:34.094* ovirt_imageio_common/qemuimg.py:11: in <module>00:02:34.094 from . compat import subprocess*00:02:34.095* ovirt_imageio_common/compat.py:12: in <module>00:02:34.095 import subprocess32 as subprocess # NOQA: F401 (unused import)00:02:34.095 E ImportError: No module named subprocess32*00:02:34.095* !!!!!!!!!!!!!!!!!!! Interrupted: 1 errors during collection !!!!!!!!!!!!!!!!!!!!00:02:34.096 =========================== 1 error in 1.06 seconds ============================
>
>
> Do we have a way to invalidate mock cache manually?
>
> Nir
>
>
>
>
>
>

Barak Korren
December 21, 2017, 7:13 PM

> fail to import the package on some slaves:

This is often the result of the packages not being installable (often because of missing repos) - unfortunately mock ignores that silently because yum does e.g. when doing 'yum install a b c' will not result in an error is 'b' is not installable.

> Do we have a way to invalidate mock cache manually?

The cache is keyed by the checksums of the '*.packages' and '*.repos' files, so changing them invalidates it

Barak Korren
December 21, 2017, 7:18 PM

Please confirm this can be closed as (another) duplicate of

Barak Korren
December 21, 2017, 8:42 PM

Closing as a duplicate.

Eyal Edri
December 24, 2017, 7:00 AM

The only way I know to 'invalidate' old pkg in mock is to specify the
version you need in .packages ( i.e >= $ver ).
Otherwise, the mock cache should expire in 2 days.

On Thu, Dec 21, 2017 at 6:08 PM, Nir Soffer <nsoffer@redhat.com> wrote:

> Forgot to add links to failing builds:
> http://jenkins.ovirt.org/job/ovirt-imageio_master_check-
> patch-fc25-x86_64/490/console
> http://jenkins.ovirt.org/job/ovirt-imageio_master_check-
> patch-fcraw-x86_64/145/console
> http://jenkins.ovirt.org/job/ovirt-imageio_master_check-
> patch-fc27-x86_64/145/console
> http://jenkins.ovirt.org/job/ovirt-imageio_master_check-
> patch-el7-x86_64/769/console
> http://jenkins.ovirt.org/job/ovirt-imageio_master_check-
> patch-fc26-x86_64/458/console
>
>
> On Thu, Dec 21, 2017 at 5:55 PM Nir Soffer <nsoffer@redhat.com> wrote:
>
>> I added 2 packages to ovirt-imageio packages files:
>> https://gerrit.ovirt.org/#/c/85639/
>>
>> The next patch using these packages
>> https://gerrit.ovirt.org/#/c/85245/
>>
>> fail to import the package on some slaves:
>>
>> 00:02:34.093 ==================================== ERRORS ====================================00:02:34.093 ____________________ ERROR collecting test/qemuimg_test.py _____________________00:02:34.093 ImportError while importing test module '/home/jenkins/workspace/ovirt-imageio_master_check-patch-el7-x86_64/ovirt-imageio/common/test/qemuimg_test.py'.00:02:34.094 Hint: make sure your test modules/packages have valid Python names.00:02:34.094 Traceback:00:02:34.094 test/qemuimg_test.py:16: in <module>00:02:34.094 from ovirt_imageio_common import qemuimg*00:02:34.094* ovirt_imageio_common/qemuimg.py:11: in <module>00:02:34.094 from . compat import subprocess*00:02:34.095* ovirt_imageio_common/compat.py:12: in <module>00:02:34.095 import subprocess32 as subprocess # NOQA: F401 (unused import)00:02:34.095 E ImportError: No module named subprocess32*00:02:34.095* !!!!!!!!!!!!!!!!!!! Interrupted: 1 errors during collection !!!!!!!!!!!!!!!!!!!!00:02:34.096 =========================== 1 error in 1.06 seconds ============================
>>
>>
>> Do we have a way to invalidate mock cache manually?
>>
>> Nir
>>
>>
>>
>>
>>
>>
> _______________________________________________
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>

Eyal edri

MANAGER

RHV DevOps

EMEA VIRTUALIZATION R&D

Red Hat EMEA <https://www.redhat.com/>
<https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)

Barak Korren
December 24, 2017, 7:10 AM

this issue had already been resolved over IRC. It was not a caching issue, as cache was not used in the failing run at all. The issue was misnaming of a package. 'subrocess32' was used in the '*.packages' file instead of 'python-subprocess32'.

Assignee

infra

Reporter

Nir Soffer

Blocked By

None

Components

Priority

Medium
Configure