Bug 15966

Summary: AB-INT PTEST ARM64: qemu-ptest timeout
Product: [QA/Testing] Package Testing (ptest) Reporter: João Marcos Costa <joaomarcos.costa>
Component: ptestAssignee: Yoann Congal <yoann.congal>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: mathieu.dubois-briand, randy.macleod, richard.purdie, yoann.congal
Version: unspecified   
Target Milestone: 5.0.21   
Hardware: x86   
OS: Multiple   
Whiteboard: AB-INT
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know
Attachments:
Description Flags
logs from valkyrie.yocto.io none

Description João Marcos Costa 2025-09-08 11:56:53 UTC
Created attachment 5139 [details]
logs from valkyrie.yocto.io

There is timeout-like failure in qemu:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/2198/steps/12/logs/stdio

qemuarm64-ptest ubuntu2204-vk-arm2

Log file attached.
Comment 1 Richard Purdie 2025-09-11 14:43:43 UTC
         '# End of io tests\n'
         'Running ./unit/test-io-channel-file\n'
         'Unexpected error in qemu_open_internal() at '
         '../sources/qemu-10.0.2/util/osdep.c:352:\n'
         './unit/test-io-channel-file: Could not create '
         "'tests/test-io-channel-file.txt': No such file or directory\n"
         'TAP version 14\n'
         '# random seed: R02S9f87f904e3d803c0bca753c648da21d2\n'
         '1..5\n'
         '# Start of io tests\n'
         '# Start of channel tests\n'
         'Running ./unit/test-nested-aio-poll\n'
Comment 2 Antonin Godard 2026-01-23 08:06:24 UTC
Looks like the same issue?

Logs were saved by Richard here:
https://valkyrie.yocto.io/pub/shared-failure-data/qemuarm64-tc-nfsshutdown/qemurunner_log.20260122004356

Quoting Richard on IRC:
"you can see it reboot after 18s in the log yet the test never exited until the 120s timeout"

qemuarm64-tc ubuntu2404-vk-3 master-next&master completed at 2026-01-22 01:31:59+00:00
https://valkyrie.yocto.io/pub/non-release/20260121-115/testresults/qemuarm64-tc/
https://autobuilder.yoctoproject.org/valkyrie/#/builders/5/builds/3012/steps/13/logs/stdio
Comment 3 Yoann Congal 2026-03-19 23:00:13 UTC
whinlatter qemuarm64-ptest ubuntu2204-vk-arm2 https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/3298

PASS: 9 /locking/co-mutex
# Start of co-mutex tests
PASS: 10 /locking/co-mutex/lockable
# End of co-mutex tests
# Start of co-rwlock tests
PASS: 11 /locking/co-rwlock/upgrade
PASS: 12 /locking/co-rwlock/downgrade
# End of co-rwlock tests
# End of locking tests
Running ./unit/test-nested-aio-poll
[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x413fd0c1]
[    0.000000] Linux version 6.16.11-yocto-standard (oe-user@oe-host) (aarch64-poky-linux-gcc (GCC) 15.2.0, GNU ld (GNU Binutils) 2.45.0.20250908) #1 SMP PREEMPT Mon Oct  6 13:50:41 UTC 2025
[    0.000000] random: crng init done
[    0.000000] Machine model: linux,dummy-virt
[    0.000000] Memory limited to 1024MB
[    0.000000] efi: UEFI not found.
[    0.000000] OF: reserved mem: Reserved memory: No reserved-memory node in the DT
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000040000000-0x000000007fffffff]

(Log from tests concatenated with dmesg output is indicative of a timeout in ptest-runner)

Maybe backport "ptest-runner: Upgrade 2.4.5.1 -> 2.5.0" ?
https://git.openembedded.org/openembedded-core/commit/?id=869d70d46c8e31cfc380b5143059cab3713cae26
Comment 4 Randy MacLeod 2026-04-15 20:05:56 UTC
Three failures that seem to be the same root cause based on comments.
Do we want to backport a newer version of ptest-runner as Yoann suggested?
Comment 5 Yoann Congal 2026-04-23 15:25:59 UTC
ptest-runner upgraded on whinlatter branch:
* ptest-runner: Upgrade 2.4.5.1 -> 2.5.0
  https://git.openembedded.org/openembedded-core/commit/?h=whinlatter&id=31bf35f2ac53dd323ec5da1d38595bcaf3127087
* ptest-runner: Upgrade 2.5.0 -> 2.5.1
  https://git.openembedded.org/openembedded-core/commit/?h=whinlatter&id=e0de7f715cc1db6c3c5a86fd7105fb0614c26bf3

I still need to backport on scarthgap. Taking the bug to track this.
Comment 6 Yoann Congal 2026-10-27 08:28:35 UTC
(In reply to Yoann Congal from comment #5)
> ptest-runner upgraded on whinlatter branch:
> * ptest-runner: Upgrade 2.4.5.1 -> 2.5.0
>  
> https://git.openembedded.org/openembedded-core/commit/
> ?h=whinlatter&id=31bf35f2ac53dd323ec5da1d38595bcaf3127087
> * ptest-runner: Upgrade 2.5.0 -> 2.5.1
>  
> https://git.openembedded.org/openembedded-core/commit/
> ?h=whinlatter&id=e0de7f715cc1db6c3c5a86fd7105fb0614c26bf3
> 
> I still need to backport on scarthgap. Taking the bug to track this.

On scarthgap: ptest-runner: Upgrade 2.5.0 -> 2.5.1
https://git.openembedded.org/openembedded-core/commit/?h=scarthgap&id=b969018b72abd96e4b504a23cb7054db4f661761