Bug 15119

Summary: ptests randomly have no results
Product: [QA/Testing] Package Testing (ptest) Reporter: Alexandre Belloni <alexandre.belloni>
Component: ptestAssignee: Ross Burton <ross.burton>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium+ CC: randy.macleod, tgamblin
Version: unspecified   
Target Milestone: 4.3 M3   
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 Alexandre Belloni 2023-05-11 15:27:51 UTC
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/4829/steps/12/logs/stdio

AssertionError: 
ptests which had no test results:
['gdbm']
Comment 1 Ross Burton 2023-05-18 16:50:31 UTC
Happened once, and according to the log the test suite did nothing:

START: ptest-runner
2023-05-06T18:34
BEGIN: /usr/lib/gdbm/ptest
DURATION: 3
END: /usr/lib/gdbm/ptest
2023-05-06T18:34
STOP: ptest-runner
TOTAL: 1 FAIL: 0

No errors, no output, nothing.

I've got a small change to remove the sed which might make any errors clearer.

Leaving open and we'll see if it happens again.
Comment 3 Ross Burton 2023-05-18 20:58:53 UTC
Ok that's weird and not the problem I thought it was.
Comment 4 Alexandre Belloni 2023-05-18 21:23:21 UTC
An other older cpio occurrence:

https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/4820/steps/12/logs/stdio
Comment 5 Trevor Gamblin 2023-06-21 19:39:17 UTC
I ran the gdbm ptests 3000 times using core-image-ptest-gdbm and didn't encounter that failure even once. My system wasn't under heavy load and the qemuparams were pretty minimal ("runqemu kvm nographic"). Makes me think that this is either another context-dependent failure or the issue has been fixed by change merged since the last reports.
Comment 6 Ross Burton 2023-06-22 08:15:48 UTC
https://git.yoctoproject.org/poky/commit/?h=master-next&id=55b0208c333e01778b25a1bdcb642ea6608e8f14 _should_ be the fix and suggests that it is a race.

I'm going to provisionally close this and we can reopen if it happens again.