16430 2026-09-17 21:28:59 +0000 [wrynose] AB-INT PTEST: timeout in openssl ptests 2026-09-24 14:39:00 +0000 1 1 10 QA/Testing Package Testing (ptest) ptest 6.0.2 x86 Multiple NEW AB-INT Medium normal 6.0.5 1 yoann.congal yoann.congal pratik.farkase randy.macleod --- --- No (bug/feature does not impact docs) oldest_to_newest 106880 0 yoann.congal 2026-09-17 21:28:59 +0000 https://autobuilder.yoctoproject.org/valkyrie/?#/builders/110/builds/1193 qemux86-64-musl-ptest debian12-vk-3 wrynose completed at 2026-09-15 19:16:02+00:00 [...] SKIP: 95-test_external_tlsfuzzer.t ............ skipped: No external tests in this configuration PASS: 99-test_ecstress.t ...................... ok PASS: 80-test_cmp_http.t ...................... ok PASS: 90-test_threads.t ....................... ok Timeout! System state: Collected system state: + dmesg [ 0.000000] Linux version 6.18.48-yocto-standard (oe-user@oe-host) (x86_64-poky-linux-musl-gcc (GCC) 15.3.0, GNU ld (GNU Binutils) 2.46.1.20260718) #1 SMP PREEMPT_DYNAMIC Tue Sep 1 21:35:47 UTC 2026 [ 0.000000] Command line: root=/dev/vda rw ip=192.168.7.24::192.168.7.23:255.255.255.0::eth0:off:8.8.8.8 net.ifnames=0 console=ttyS0 console=ttyS1 oprofile.timer=1 tsc=reliable no_timer_check rcupdate.rcu_expedited=1 swiotlb=0 printk.time=1 [...] 106889 1 pratik.farkase 2026-09-18 10:36:29 +0000 Hi Yoann, Sent a proposed fix here : https://lists.openembedded.org/g/openembedded-core/message/246210 let's see if it happens again on the autobuilder 106890 2 yoann.congal 2026-09-18 12:39:36 +0000 (In reply to Pratik Farkase from comment #1) > Hi Yoann, > > Sent a proposed fix here : > https://lists.openembedded.org/g/openembedded-core/message/246210 > > let's see if it happens again on the autobuilder For reference, patch is "core-image-ptest: raise ptest timeout for openssl" and I answered: > On the patch content itself, we don't usually increase timeout without a > good reason like high AB-INT frequency, analysis to show that this is > the right solution. > In this case, if you want to look at this bug, I think you should try to > determine what happened. For example, which test triggered the timeout? > Is this test prone to load related issues? Is there a related issue > upstream? a fix? ... > If you don't want to look at this, I'm fine with waiting to see if how > often it reproduces (if ever).