In https://bugzilla.yoctoproject.org/show_bug.cgi?id=16163 analysis showed that one of the root causes is the hard coded 450 second timeout passed to ptest-runner in lib/oeqa/runtime/cases/ptest.py.
This series introduces the PTEST_RUNNER_TIMEOUT variable, which is consumed in lib/oeqa/runtime/cases/ptest.py but needs to be updated in testimage.bbclass to make sure the value of the variable is consumed at runtime. For python3-cffi which drove the change, the value is set in core-image-ptest.bb to 600 seconds, as an example of how a per recipe change can be enabled. The test run on the AutoBuilder cluster that proves this works is: https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/3136 https://valkyrie.yocto.io/pub/non-release/20260227-113/testresults/qemuarm64-ptest/core-image-ptest-python3-cffi/ where you can see: PATH=/usr/sbin:/sbin:/usr/bin:/bin; ptest-runner -t 600 -d "/usr/lib" in https://valkyrie.yocto.io/pub/non-release/20260227-113/testresults/qemuarm64-ptest/core-image-ptest-python3-cffi/log.do_testimage.2323256.20260227191837 [YOCTO #16163] Tim Orling (3): oeqa/runtime/ptest: Make ptest-runner timeout configurable core-image-ptest: add PTEST_RUNNER_TIMEOUT testimage.bbclass: enable PTEST_RUNNER_TIMEOUT variable meta/classes-recipe/testimage.bbclass | 4 +++- meta/lib/oeqa/runtime/cases/ptest.py | 3 ++- meta/recipes-core/images/core-image-ptest.bb | 1 + 3 files changed, 6 insertions(+), 2 deletions(-) -- 2.50.1 (Apple Git-155)
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#232111): https://lists.openembedded.org/g/openembedded-core/message/232111 Mute This Topic: https://lists.openembedded.org/mt/118036273/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
