It would be very useful to be able to know how long each individual ptest takes to run and be able to pass this data from ptest-runner through to the xml results logging from testimage so it ends up in the standard test results. I believe we have some ptests which are taking too long and ending up being 'killed' for timing out but its hard to obtain that data from the logs. Creating a "dummy" timeout failure in the test results may also be something we need to look at as a way of flagging timeouts up the chain of test reporting.
(In reply to comment #0) > It would be very useful to be able to know how long each individual ptest > takes to run and be able to pass this data from ptest-runner through to the > xml results logging from testimage so it ends up in the standard test > results. > > I believe we have some ptests which are taking too long and ending up being > 'killed' for timing out but its hard to obtain that data from the logs. > > Creating a "dummy" timeout failure in the test results may also be something > we need to look at as a way of flagging timeouts up the chain of test > reporting. Currently is printing TIMEOUT in the stdout [1], I can add a xml dummy failure for timeout that will display when status in exit is SIGKILL [2]. Is that the idea? [2] [1] http://git.yoctoproject.org/cgit/cgit.cgi/ptest-runner2/tree/utils.c#n320 [2] http://git.yoctoproject.org/cgit/cgit.cgi/ptest-runner2/tree/utils.c#n432
At, https://lists.yoctoproject.org/pipermail/yocto/2019-January/043703.html
(In reply to comment #2) > At, > > https://lists.yoctoproject.org/pipermail/yocto/2019-January/043703.html Added report duration support, https://lists.yoctoproject.org/pipermail/yocto/2019-January/043724.html
Merge at, http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=b1c2ef099cdb49655f4ae0d9cf9c5baef997e833 http://git.yoctoproject.org/cgit/cgit.cgi/ptest-runner2/commit/?id=80712583732b4a809532f644fb09e7d2e812d7ba