Created attachment 5105 [details] logs https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/583/steps/12/logs/stdio Failed ptests:{'python3': ['test_extractall_none_mtime', 'python3']} qemuarm64-ptest ubuntu2410-vk-arm1
FAIL: test_extractall_none_mtime (test.test_tarfile.NoneInfoExtractTests_Tar.test_extractall_none_mtime) (path=PosixPath('/var/volatile/tmp/test_python_0yxmmpt7/test_python_16329æ/@test_16329_tmpæ-tardir/extractall_none/pax/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123/123')) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/lib/python3.13/test/test_tarfile.py", line 3270, in test_extractall_none_mtime self.assertGreaterEqual(path.stat().st_mtime, now) ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^ AssertionError: 1734189417.9550788 not greater than or equal to 1734193017.9396935
So... the parent folder was created _after_ the files inside it. Great. But the difference between them is 3599.9846147 seconds, or (almost) exactly one hour. That probably means something important.
The odd timestamps are interesting but this only occurred once and hasn't happened in a year so resolving.
qemux86-64-musl-ptest debian12-vk-4 mathieu/master-next completed at 2026-06-09 08:48:21+00:00 https://valkyrie.yocto.io/pub/non-release/20260609-56/testresults/qemux86-64-musl-ptest/ https://autobuilder.yoctoproject.org/valkyrie/#/builders/110/builds/505/steps/13/logs/stdio
qemux86-64-musl-ptest debian12-vk-6 master&master-next completed at 2026-06-13 18:24:13+00:00 https://valkyrie.yocto.io/pub/non-release/20260613-102/testresults/qemux86-64-musl-ptest/ https://autobuilder.yoctoproject.org/valkyrie/#/builders/110/builds/536/steps/13/logs/stdio
https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/4909/steps/15/logs/stdio qemuarm64-ptest ubuntu2404-vk-arm2 Reopening.
FAIL: test_extractall_none_mtime (test.test_tarfile.NoneInfoExtractTests_Data.test_extractall_none_mtime) (path=PosixPath('/var/volatile/tmp/test_python_0 c2fdsmi/test_python_17795√¶/@test_17795_tmp√¶-tardir/extractall_none/gnu/123/123/123/123/123')) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/lib/python3.14/test/test_tarfile.py", line 3581, in test_extractall_none_mtime self.assertGreaterEqual(path.stat().st_mtime, now) ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^ AssertionError: 1794589993.9077852 not greater than or equal to 1794593593.9003344
1794593593.9003344-1794589993.9077852=3599.9925492 Ah hour, again. I'm wondering if there's a test running in parallel that changes the time!
Look what I found: def test_monotonic_settime(self): t1 = time.monotonic() realtime = time.clock_gettime(time.CLOCK_REALTIME) # jump backward with an offset of 1 hour try: time.clock_settime(time.CLOCK_REALTIME, realtime - 3600)
Filed https://github.com/python/cpython/issues/162280 about the general issue of changing system time during a test run. We can skip that test, I hope that's the only instance.
"python3: skip test_monotonic_settime() test case" posted.