On Wed, 2019-04-17 at 22:55 +0100, Richard Purdie wrote: > I mentioned differences in numbers of pass/fail depending on which > image you install ptests into. The recipes which have the issues and > the numbers are: > > core-image-sato with ptest installed: > > Recipe | Passed | Failed | Skipped | > > diffutils | 20 | 0 | 1 | > elfutils | 31 | 6 | 166 | > flex | 0 | 0 | 0 | > gzip | 3 | 19 | 0 | > libxml-parser-perl | 0 | 15 | 0 | > lttng-tools | 3397 | 626 | 1 | T > nettle | 95 | 2 | 2 | > openssh | 0 | 0 | 1 | > perl | 2425 | 20 | 235 | > python | 304 | 6 | 39 | > python3 | 30321 | 2 | 1019 | > quilt | 23 | 34 | 0 | > tcl | 148 | 1 | 0 | > util-linux | 378 | 2 | 58 | > valgrind | 0 | 0 | 0 |
The testresults.json file for these tests is: https://autobuilder.yocto.io/pub/non-release/20190417-10/testresults/qemux86-64-ptest/testresults.json To get the report above you can: wget https://autobuilder.yocto.io/pub/non-release/20190417-10/testresults/qemux86-64-ptest/testresults.json /path/to/oe-core/scripts/resulttool report testresults.json To get the test log output you can: wget https://autobuilder.yocto.io/pub/non-release/20190417-10/testresults/qemux86-64-ptest/testresults.json /path/to/oe-core/scripts/resulttool store testresults.json /path/to/new-results-gitrepo cd /path/to/new-results-gitrepo git checkout master-next less repo/runtime/poky/qemux86-64/core-image-sato-ptest/ptest-lttng-tools.log > core-image-sato-sdk with ptest installed: > > Recipe | Passed | Failed | Skipped | > > diffutils | 21 | 0 | 0 | > elfutils | 31 | 4 | 168 | > flex | 114 | 0 | 0 | > gzip | 22 | 0 | 0 | > libxml-parser-perl | 15 | 0 | 0 | > lttng-tools | 4693 | 1 | 412 | > nettle | 96 | 1 | 2 | > openssh | 67 | 0 | 3 | > perl | 2430 | 19 | 231 | > python | 131 | 1 | 17 | > python3 | 30329 | 2 | 1011 | > quilt | 57 | 0 | 0 | > tcl | 149 | 0 | 0 | > util-linux | 473 | 2 | 52 | > valgrind | 297 | 251 | 31 | For these the testresults.json file is: https://autobuilder.yocto.io/pub/non-release/20190417-14/testresults/qemux86-64-ptest/testresults.json Commands to diving into this are similar to the above. I would like to: a) teach resulttool how to handle http urls itself b) add a command just to dump the ptest logs to the current directory c) add the logs to the autobuilder http:// urls magically but simply haven't gotten there with those yet, the tool itself is clearly nearly there! Cheers, Richard -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core