Hi Mathieu, Thanks for testing and confirming the issue.
I've investigated the test failures. The problem is that test_lazy() requires html.parser to not be in sys.modules, but when test_move_items() runs first (which happens in pytest's alphabetical order), it imports these modules, causing test_lazy() and the related test_move_items parametrized tests to fail. This appears to be a test order dependency issue in six's test suite itself, not specific to Yocto. I have two options to fix this: 1. Patch six's test_six.py to clean up module state before test_lazy runs (but this modifies upstream test code) 2. Skip these problematic tests in run-ptest for now (cleaner for Yocto, but reduces test coverage) Which approach would you prefer? Or do you have other suggestions? Thanks, Shilong Jiao ________________________________ From: Mathieu Dubois-Briand <[email protected]> Sent: Wednesday, June 10, 2026 20:55 To: Jiao, Shilong <[email protected]>; [email protected] <[email protected]>; Jiao, Shilong <[email protected]> Subject: Re: [OE-core] [PATCH] python3-six: Add ptest support CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. On Tue Jun 9, 2026 at 12:09 PM CEST, Shilong via lists.openembedded.org Jiao wrote: > Hi, > > Quick update on my investigation: > > I've tested these failing cases locally in my build environment, and > interestingly all 8 tests pass: > - test_lazy: PASS > - test_move_items[html_entities]: PASS > - test_move_items[html_parser]: PASS > - test_move_items[BaseHTTPServer]: PASS > - test_move_items[CGIHTTPServer]: PASS > - test_move_items[SimpleHTTPServer]: PASS > - test_move_items[xmlrpc_client]: PASS > - test_move_items[xmlrpc_server]: PASS > > This suggests the failures might be specific to the autobuilder environment > or related to test execution order. The test_lazy failure in particular > looks like it could be caused by html.parser already being imported when > the test runs. > > Could you help me access the detailed error messages from the autobuilder > logs? This would help me understand the actual failure mode and create an > appropriate fix. > > Thanks, > Shilong Jiao > ________________________________ Hi, The autobuilder configuration is described in the "Write config" step of the build. I did reproduce this issue locally with following layers: BBLAYERS ?= " \ .../openembedded-core/meta \ .../meta-yocto/meta-poky \ .../meta-yocto/meta-yocto-bsp \ .../openembedded-core/meta-selftest \ " And following lines in my local.conf: SDKMACHINE = "x86_64" PACKAGE_CLASSES = "package_rpm package_deb package_ipk" INHERIT += 'image-buildinfo' IMAGE_BUILDINFO_VARS:append = ' IMAGE_BASENAME IMAGE_NAME' TEST_SUITES = 'ping ssh ptest' SANITY_TESTED_DISTROS = '' OEQA_TESTDISPLAY = ':1' OE_FRAGMENTS += 'core/yocto-autobuilder/autobuilder core/yocto-autobuilder/autobuilder-resource-constraints' EXTRA_IMAGE_FEATURES ?= 'allow-empty-password empty-root-password allow-root-login' OE_FRAGMENTS += 'machine/qemux86-64 distro/poky' 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 (#238418): https://lists.openembedded.org/g/openembedded-core/message/238418 Mute This Topic: https://lists.openembedded.org/mt/119716979/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
