Bug 16430

Summary:	[wrynose] AB-INT PTEST: timeout in openssl ptests
Product:	[QA/Testing] Package Testing (ptest)	Reporter:	Yoann Congal <yoann.congal>
Component:	ptest	Assignee:	Yoann Congal <yoann.congal>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	Medium	CC:	pratik.farkase, randy.macleod
Version:	6.0.2
Target Milestone:	6.0.5
Hardware:	x86
OS:	Multiple
Whiteboard:	AB-INT
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Yoann Congal 2026-09-17 21:28:59 UTC

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
[...]

Comment 1 Pratik Farkase 2026-09-18 10:36:29 UTC

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

Comment 2 Yoann Congal 2026-09-18 12:39:36 UTC

(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).