#13 Skip test failing with mock 5.0
Closed 2 months ago by yselkowitz. Opened 6 months ago by yselkowitz.
rpms/ yselkowitz/python-dateutil rawhide  into  rawhide

file modified
+2 -1
@@ -83,7 +83,8 @@ 



  %if %{with tests}

- %{__python3} -m pytest -W ignore::pytest.PytestUnknownMarkWarning

+ # test_tzlocal_local_time_trim_colon fails with mock 5.0

+ %{__python3} -m pytest -W ignore::pytest.PytestUnknownMarkWarning -k 'not test_tzlocal_local_time_trim_colon'


  %py3_check_import dateutil dateutil.easter dateutil.parser dateutil.relativedelta dateutil.rrule dateutil.tz dateutil.utils dateutil.zoneinfo


Rebuilding python-dateutil in at least f38+ now fails; my best guess is that it's related to mock 5, but I could be wrong about that.

Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci

I cannot reproduce the failure on Fedora 37 with mock 5.0.

Can you reproduce on f38+? If it's not mock, then what?

No, running the rawhide build in rawhide mock chroot running mock 5.0 in Fedora 38 podman container and still no test failure.

This is what I'm seeing, running mock 5.0 in a f38 toolbox:

=================================== FAILURES ===================================
______________________ test_tzlocal_local_time_trim_colon ______________________

    def test_tzlocal_local_time_trim_colon():
        with TZEnvContext(':/etc/localtime'):
>           assert tz.gettz() is not None
E           assert None is not None
E            +  where None = <dateutil.tz.tz.__get_gettz.<locals>.GettzFunc object at 0x7f603fd05190>()
E            +    where <dateutil.tz.tz.__get_gettz.<locals>.GettzFunc object at 0x7f603fd05190> = tz.gettz

dateutil/test/test_tz.py:990: AssertionError
=========================== short test summary info ============================
FAILED dateutil/test/test_tz.py::test_tzlocal_local_time_trim_colon - assert ...
============ 1 failed, 2020 passed, 47 skipped, 17 xfailed in 4.67s ============

Scratch builds are indeterminate at the moment, as koji appears to still be using mock 4.1.

Still seeing this. Could it be related to running mock in a toolbox? Can anyone reproduce this in a toolbox with either mock 4.1 or 5.0?

I don't use toolbox, could you please provide instructions?

Pull-Request has been closed by yselkowitz

2 months ago