4114 2013-03-26 15:44:11 +0000 Add ptest integration 2014-09-29 13:09:04 +0000 1 1 10 QA/Testing Test Plans/Suite test-plans/suite unspecified All Multiple VERIFIED FIXED High enhancement 1.7 M3 4680 1 bjst georgex.l.musat alexandru.c.georgescu atul.singh008 bluelightning corneliux.stoicescu elizabeth.flanagan richard.purdie sgw sstncr andrax.g.necula --- --- No (bug/feature does not impact docs) oldest_to_newest 31173 0 bjst 2013-03-26 15:44:11 +0000 Ptests should be ran, and results interpreted, as part of automatic testing. 32723 1 bluelightning 2013-04-29 15:29:05 +0000 From Richard's recent comments, this would need us to: * Enable ptest to run from the qemuimagetests * Find a way to collect up the ptest results (log into buildhistory so we can compare tests results to previous runs?). Important detail is when test results which did pass start failing. 32941 2 sstncr 2013-05-08 09:24:25 +0000 I'll take shot at this. I've started something here: http://git.yoctoproject.org/cgit.cgi/poky-contrib/?h=stefans%2Fqemu-ptest1 specifically the first part: enable ptest to run from the qemuimagetests I've tested a core-image-sato with the following in local.conf: DISTRO_FEATURES_append = " ptest" IMAGE_FEATURES_append = " ptest-pkgs tools-sdk" IMAGE_INSTALL_append = " ptest-runner dbus bash glib-2.0" IMAGETEST = "qemu" TEST_SCEN = "standalone:ptest" I have some issues: - running ptest takes a long time, right know I've used 850 seconds as a timeout but that's not enough. I want to add support in qemuimagetest for passing arguments to runqemu (arguments like kvm and qemuparams="-m 1024"), and that should help. - there are tests which fail and are known to fail - how to exclude them. - I have no idea on how to integrate the results in buildhistory from qemutests. Help? 32942 3 bjst 2013-05-08 09:48:55 +0000 Yes, ptests can take a very long time. And obviously the time varies for different targets too. In our system we use a timeout per line instead of per command, so that as long as the tests produce output they don't time out. The ptests recipes in dylan still have some bugs, causing more test failures than necessary (and possibly timeouts). I will submit patches for that shortly. As for integrating with qemuimagetest, I don't know. We are using an expect script to boot and run all targets in buildbot, both qemu and hardware boards. We run this in autobuilder and parse the logs to extract results. I think we should have a discussion about how to implement automatic testing in a way so it is easy for people to set up and run auto tests in their projects and on their hardware. 33139 4 sstncr 2013-05-17 15:09:20 +0000 (In reply to comment #3) > Yes, ptests can take a very long time. And obviously the time varies for > different targets too. In our system we use a timeout per line instead of > per command, so that as long as the tests produce output they don't time out. > Hmm, this might be a good idea. I'll think about it. > The ptests recipes in dylan still have some bugs, causing more test failures > than necessary (and possibly timeouts). I will submit patches for that > shortly. > Ok, great. > As for integrating with qemuimagetest, I don't know. We are using an expect > script to boot and run all targets in buildbot, both qemu and hardware > boards. We run this in autobuilder and parse the logs to extract results. > The thing is we don't want to tie people to the autobuilder to run these tests. Some people might use other build systems (like jenkins). That's way we want the tests to be run as part of qemuimagetest. These way they can be fired off from a command line too. The bad thing is that doesn't integrate with real hardware. After some changes to qemuimagetest went in master: - we can now pass qemuparams="-m 1024" and that helps a lot - a timeout can be specified to Test_SSH now, before it was limited to 50 seconds. That helped me with the long running part and timeouts. Given that and the top 2 commits from http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=stefans/qemu-ptest2 now I can succesfully run a sato image and get the log file. If the image it's built with INHERIT += "buildhistory" the ptest log will be copied in buildhistory dir. I'm wondering if that's enough for tracking. > I think we should have a discussion about how to implement automatic testing > in a way so it is easy for people to set up and run auto tests in their > projects and on their hardware. I think that will be great. 36678 5 sstncr 2013-09-13 12:53:29 +0000 Unfortunately I don't think anything usable will make it in 1.5, so I'm bumping the target milestone. Also, as the qemuimagetest is obsolete by testimage.bbclass, I've make an attempt at a skeleton implementation here: http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=stefans/run-ptest1&id=b9e86394684f2c3809b3539cbe6b67e28e4d96cf It just runs ptest-runner and copies the log to buildhistory dir but it doesn't do any "check" of the results. The good part is that testimage already had support for restart the target with more memory (but now qemu have 256 by default so it's okay) and for setting longer or no timeouts. And if testimage will know about real hardware this will just work. (either from an AB setup or fired off from command line). 45486 6 georgex.l.musat 2014-09-09 10:41:12 +0000 Ptest runtime test has been developed and it's waiting review 45674 7 richard.purdie 2014-09-18 14:54:35 +0000 Code merged to master http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=7c16a538bc57116b87cf1912e7f4a460b38e015c 45937 8 andrax.g.necula 2014-09-29 13:09:04 +0000 Verified on commit 8ac8eca2e3bd8c78e2b31ea974930ed0243258a3.