https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/4829/steps/12/logs/stdio AssertionError: ptests which had no test results: ['gdbm']
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.
libnl occurrence: https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/5061/steps/12/logs/stdio cpio occurrence: https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/5010/steps/12/logs/stdio
Ok that's weird and not the problem I thought it was.
An other older cpio occurrence: https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/4820/steps/12/logs/stdio
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.
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.