There is one component that has been identified that runs as part of the ptest execution and gets no report out of it. The flex component is enabled and run as part of the execution but it is presenting a bogus behavior that prevents it from reporting a PASS/FAIL result. The script that is parsing the ptest log searching for results is skipping the flex component reports even though it presented the following lines: START: ptest-runner BEGIN: /usr/lib/flex/ptest I would propose that the parser fails instead of just ignoring the lack of results. It is required at this moment to see if there are other components in this situation.
Edwin, in case you want to easily reproduced this issue, just revert 66aebcc: Leonardo Sandoval: Wed Jun 15 18:05:22 2016 +0100: flex: Fix top_builddir path for flex's test-driver script And run the ptest-runner. This patch is the one correcting the flex issue, so reverting it would allow to reproduce what Benjamin observed.
Added error coverage to support when launching child process fails. Patch sent to Anibal Limon
https://lists.yoctoproject.org/pipermail/yocto/2016-September/032078.html
V2 https://lists.yoctoproject.org/pipermail/yocto/2016-September/032079.html
Patch Version 4 (It is additionally including unit test code) https://lists.yoctoproject.org/pipermail/yocto/2016-September/032104.html
(In reply to comment #5) > Patch Version 4 (It is additionally including unit test code) > https://lists.yoctoproject.org/pipermail/yocto/2016-September/032104.html Edwin, I just integrated your code into and created a tag v2.0.1 since is a minor fix, http://git.yoctoproject.org/cgit/cgit.cgi/ptest-runner2/log/ Please update the recipe and send the patch to oe-core.
the patch to oe-core http://lists.openembedded.org/pipermail/openembedded-core/2016-September/126887.html
Patch merge http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=6c22e39f06dac92698e98172c509f3671743e92f