WARNING: core-image-ptest-gnutls-1.0-r0 do_testimage: There were failing ptests. Traceback (most recent call last): File "/home/pokybuild/yocto-worker/qemuarm64-ptest/build/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f return func(*args, **kwargs) File "/home/pokybuild/yocto-worker/qemuarm64-ptest/build/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f return func(*args, **kwargs) File "/home/pokybuild/yocto-worker/qemuarm64-ptest/build/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f return func(*args, **kwargs) File "/home/pokybuild/yocto-worker/qemuarm64-ptest/build/meta/lib/oeqa/runtime/cases/ptest.py", line 27, in test_ptestrunner_expectfail self.do_ptestrunner() File "/home/pokybuild/yocto-worker/qemuarm64-ptest/build/meta/lib/oeqa/runtime/cases/ptest.py", line 120, in do_ptestrunner self.fail(failmsg) AssertionError: Failed ptests: {'gnutls': ['naked-alerts']} https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/5925/steps/12/logs/stdio qemuarm64-ptest ubuntu2204-arm-1
https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/5776/steps/12/logs/stdio qemux86-64-ptest debian11-ty-1
https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/6076/steps/13/logs/stdio qemux86-64-ptest opensuse154-ty-3
Tried to reproduce it within qemux86-64 ptest-image and just with make check based upon gnutls sources. No luck so far. Is there any way to obtain this log https://git.yoctoproject.org/poky/tree/meta/recipes-support/gnutls/gnutls/run-ptest#n56 from the autobuilder upon failure? That might help to understand why it fails
Simone, Yes that should be possible but we don't want to gather too much data. I don't think there's a ptest example to copy but I could be wrong... Can you dive into: https://git.yoctoproject.org/yocto-autobuilder-helper/log/?qt=grep&q=collect and see what you can figure out. I did some work with Sakib Sajal and Aryaman Gupta a while ago on collecting host data to help understand the intermittent build failures that we were seeing so I might be able to help out if needed. The data could be available via: https://autobuilder.yocto.io/pub/non-release/ for example see this intermittent build failure log: https://autobuilder.yocto.io/pub/non-release/20240201-30/testresults/qemuarm64-ptest/intermittent_failure_host_data/host_stats_interval_2_top_summary.txt which is part of this larger run: https://autobuilder.yocto.io/pub/non-release/20240201-30/testresults/ We also sample the buildhistory logs using: https://git.yoctoproject.org/yocto-autobuilder-helper/tree/scripts/archive_buildstats.py so maybe that will help. If all of this is too much to grok, just ask on the yocto list or irc or ask me to invite you to a YP Autobuilder discussion call (Thursday's 9 AM ET).
Simone, Alex Belloni tells me that: "This" is the goal of our high bug.: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14901 We would be able to configure per recipe which log we want to lift out of the host or guest on test failure
ThX Randy, I will see what I can work out
Simone, bumped to 5.1-M2. Hopefully you'll make/find time to work on this bug. Thanks, Randy for the YP bug review
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/6600/steps/13/logs/stdio qemuarm64-ptest ubuntu1804-arm-1
Any news Simone?
Not seen in a while and only happened once on the slow arm builder. Better logging would be useful but resolving anyway...