| Summary: | Add support for extracting individual ptest timing | ||
|---|---|---|---|
| Product: | [QA/Testing] Package Testing (ptest) | Reporter: | Richard Purdie <richard.purdie> |
| Component: | ptest | Assignee: | Aníbal Limón <anibal> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium+ | CC: | ndec13, randy.macleod |
| Version: | unspecified | ||
| Target Milestone: | 2.7 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Richard Purdie
2018-12-17 16:59:53 UTC
(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 (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 |