Bug 15009

Summary: Ptest END log section mismatch No-section vs. python3-pluggy
Product: [QA/Testing] Package Testing (ptest) Reporter: Luca Ceresoli <luca.ceresoli>
Component: ptestAssignee: Unassigned <unassigned>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: alexandre.belloni, luca.ceresoli, randy.macleod, richard.purdie, ross.burton
Version: unspecified   
Target Milestone: 4.3   
Hardware: x86   
OS: Multiple   
Whiteboard: AB-INT AB-HAVE-PLAN
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Luca Ceresoli 2023-01-18 08:35:45 UTC
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/4366/steps/12/logs/stdio

qemuarm64-ptest on ubuntu2004-arm-1


NOTE: Running task 1140 of 1140 (/home/pokybuild/yocto-worker/qemuarm64-ptest/build/meta/recipes-core/images/core-image-ptest-all.bb:do_testimage)
NOTE: recipe core-image-ptest-all-1.0-r0: task do_testimage: Started
QMP Available for connection at /home/pokybuild/yocto-worker/qemuarm64-ptest/build/build/tmp/.sqbue0ry
QMP connected to QEMU at 01/17/23 07:25:31 and took 3.6918752193450928 seconds
QMP released QEMU at 01/17/23 07:25:31 and took 0.2932164669036865 seconds from connect
Bitbake still alive (no events for 600s). Active tasks:
/home/pokybuild/yocto-worker/qemuarm64-ptest/build/meta/recipes-core/images/core-image-ptest-all.bb:do_testimage
...
Bitbake still alive (no events for 16200s). Active tasks:
/home/pokybuild/yocto-worker/qemuarm64-ptest/build/meta/recipes-core/images/core-image-ptest-all.bb:do_testimage
WARNING: core-image-ptest-all-1.0-r0 do_testimage: Ptest END log section mismatch No-section vs. python3-pluggy


According to Alexandre Belloni:
> the issue is in the testresults.json generation
> I would say that two processes are working in the file
Comment 2 Randy MacLeod 2023-01-19 15:40:36 UTC
See only once so far.
Comment 3 Richard Purdie 2023-06-08 14:57:38 UTC
Need to audit locking around output file.

The no section issue also occurs on standard ptest runs on the autobuilder so we should track down where it is coming front which may give clues as to this issue.