On Thu Jan 29, 2026 at 12:22 PM CET, Leon Anavi wrote: > Hi Mathieu, > > On Wed, Jan 28, 2026 at 7:03 PM Mathieu Dubois-Briand < > [email protected]> wrote: > >> On Tue Jan 27, 2026 at 10:18 AM CET, Leon Anavi via lists.openembedded.org >> wrote: >> > Upgrade to release 0.19.1: >> > >> > - Fix SeekableZstdFile write table entries on 32-bits architectures >> > when there is a huge number of entries >> > >> > From release 0.19.0: >> > >> > - The project has been completely refactored to use the Zstandard >> > implementation from the standard library (PEP-784) >> > - The refactor has some minor impact on public APIs, such as >> > changing the exception raised on invalid input >> > - Add backports.zstd dependency for Python before 3.14 >> > - Changes in build dependency: remove setuptools and C build >> > toolchain, add hatchling and hatch-vcs >> > - Remove git submodule usage >> > - Drop support for Python 3.9 and below >> > - Use ruff as formatter and linter >> > - Embed type hints in Python code, and check with mypy >> > >> > All ptests pass following python3 upgrade from 3.13.11 to 3.14.0. >> > >> > Signed-off-by: Leon Anavi <[email protected]> >> > --- >> >> Hi Leon, >> >> Thanks for the new version. >> >> It looks like this is breaking some ptest: >> >> Failed ptests: >> {'python3-pyzstd': 'START: ptest-runner\n' >> '2026-01-28T16:27\n' >> '\n' >> ... >> "E ImportError: cannot import name 'zstd' from " >> "'compression' (unknown location)\n" >> >> https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/2996 >> https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/1005 >> >> Test results can be found here: >> >> >> https://valkyrie.yocto.io/pub/non-release/20260128-86/testresults/qemux86-64-ptest/core-image-ptest-python3-pyzstd/ >> Test results for riscv64 and arm64 are not published at this time, as >> some tests are still running. They will all end-up in >> https://valkyrie.yocto.io/pub/non-release/20260128-86/testresults/ >> >> Can you have a look at these failures? >> > > Hm, I am not exactly sure what's going on. On my Raspberry Pi 5 test > setup ptest-runner python3-pyzstd doesn't report any issues: > > Testsuite summary > # TOTAL: 209 > # PASS: 209 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 0 > # XPASS: 0 > # ERROR: 0 > DURATION: 4 > END: /usr/lib/python3-pyzstd/ptest > 2026-01-29T11:17 > STOP: ptest-runner > TOTAL: 1 FAIL: 0 > > I will take another look after FOSDEM. I will likely need to reproduce your > exact test environment. In the meantime, do you have any hints about what > might be causing the test failures on your side? > > Best regards, Leon > >
Hi Leon, I'm not really sure about what is the issue here, but maybe a different configuration or a missing dependency. If you need any data about how to reproduce it in qemu, all data should be in the build, particularly in the "Write config" step: https://autobuilder.yoctoproject.org/valkyrie/api/v2/logs/5139973/raw_inline So basically: SDKMACHINE = "x86_64" TEST_SUITES = 'ping ssh ptest' SANITY_TESTED_DISTROS = '' EXTRA_IMAGE_FEATURES ?= 'allow-empty-password empty-root-password allow-root-login' bitbake-config-build enable-fragment machine/qemux86-64 bitbake-config-build enable-fragment distro/poky bitbake core-image-ptest-python3-pyzstd bitbake -c do_testimage core-image-ptest-python3-pyzstd Please tell me if you have any issue reproducing the failure. Thanks, Mathieu -- Mathieu Dubois-Briand, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#230234): https://lists.openembedded.org/g/openembedded-core/message/230234 Mute This Topic: https://lists.openembedded.org/mt/117485653/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
