11111 2017-02-28 09:43:06 +0000 enable running oe-selftest tests in CI 2017-04-10 19:22:08 +0000 1 1 6 Yocto Project Subprojects IoT Reference OS Kit intel-iot-refkit-tools unspecified x86 Multiple RESOLVED FIXED Medium critical 2.3 M3 1 patrick.ohly olev.kartau anibal.limon benjamin.esquivel humberto.ibarra.lopez jair.de.jesus.gonzalez.plascencia mariano.lopez matti-pekka.sivosuo mikko.ylinen olev.kartau --- --- No (bug/feature does not impact docs) oldest_to_newest 70974 0 patrick.ohly 2017-02-28 09:43:06 +0000 For testing complex boot scenarios (like TPM, image-installer, etc.) we need control over booting qemu. Such testing is easy in a test based on oe-selftest and impossible with testimage.bbclass based tests, so we need to extend the refkit CI so that it invokes oe-selftest with a certain list of tests. It might be useful to have two sets: * One which is used before building. If one of these tests fails, building can be skipped because there is a fatal flaw. * One which is used after building, but only if building succeeded. These tests then can reuse build artifacts (like images) if they exist already. The sstate test that we have falls into the first set, the (to be written) image tests into the second. The sets could be defined in the CI .inc file. 70975 1 olev.kartau 2017-02-28 10:20:42 +0000 refkit CI currently does not run iotsstatetests.SStateTests.test_sstate_samesigs before building. Could it add any value running that test in refkit case? 70978 2 patrick.ohly 2017-02-28 10:53:58 +0000 (In reply to comment #1) > refkit CI currently does not run > iotsstatetests.SStateTests.test_sstate_samesigs > before building. > Could it add any value running that test in refkit case? The test would need to be updated to reflect the current set of supported machines, but yes, in principle it might still be useful. 70981 3 olev.kartau 2017-02-28 11:33:47 +0000 tried in refkit current master, takes 1min on a desktop machine. Indeed, MACHINE set needs editing in meta-refkit/lib/oeqa/selftest/iotsstatetests.py Is the idea that we keep changing that file, or should we attempt defining machine set outside of code, in some CI_ variables? 70982 4 olev.kartau 2017-02-28 11:57:36 +0000 or another idea, can we modify samesigs test so that it takes MACHINES as argument? In refkit CI, machine set to build is defined in Jenkinsfile so most convenient would be just run samesigs giving MACHINES as argument, instead of parsing machines from environment or strings defined in files etc. 70983 5 patrick.ohly 2017-02-28 12:36:51 +0000 (In reply to comment #4) > or another idea, can we modify samesigs test so that it takes > MACHINES as argument? Yes, that would be useful. I also need to check whether improvements that I made to that test could go back to OE-core. I did something (better error reporting?) but without going back to the Ostro repo I am not sure what those were. But enabling the mechanism for running oe-selftest is a bit orthogonal to actually enabling tests which use the mechanism. I'm saying "a bit" because obviously some tests are needed for testing the mechanism ;-} 70984 6 patrick.ohly 2017-02-28 15:26:40 +0000 Stephen, I think we need to keep this assigned to Olev. We need this enabled in the current Refkit CI scripts for Jenkins, and I believe Olev is still the one maintaining those. 71006 7 olev.kartau 2017-03-01 08:51:57 +0000 Let's keep this ticket for enabling running additional tests in CI, (both pre-build and after build), and create a separate ticket about creating after-build, runnable-in-qemu, tests. 71007 8 patrick.ohly 2017-03-01 09:15:53 +0000 The goal has always been to focus on "enable oe-selftest tests" (not writing them) and "extend the refkit CI so that it invokes oe-selftest with a certain list of tests". So yes, this issue here is about the CI system, not the tests using that functionality. Those were just mentioned to give a justification why such a capability in the CI system are needed, and why two slots are useful. Also note that running tests works best when they use exactly the same build configuration as the build itself (better sstate reuse). This influences how to hook the tests into the CI system. 71104 9 olev.kartau 2017-03-07 13:00:29 +0000 Refkit PR#53 has draft implementation of both pre-build and after-build selftest activation. You can check the last of 6 commits only for that, others are about Jenkinsfile refactoring, as I started to prepare for separate stage implementation for running test. Later, plan changed and test calls were inserted into build script. Test names are taken from REFKIT_CI_ variables. As pre-build, current sstate-samesigs test is used. As post-build, there are no tests yet, I verified with samesigs test that step runs. 71348 10 olev.kartau 2017-03-16 10:59:47 +0000 PR#53 now reached a next checkpoint state, please check. Per Mikko's idea, I moved BUILDHISTORY enablement from refkit-ci.inc to build-project.sh which allows to simplify conf/auto.conf creation during oe-elftest. pre- and post- tests are now as separate scripts and they will show as separate CI build phases, to allow clear status reporting from stages. Overall, this change also caused examination of other things which leads to multiple commits with cleanup and re-structure. for example, we were still running several CI-only-related steps in local build, which is avoided in PR#53 current state of code. 71444 11 olev.kartau 2017-03-20 08:21:27 +0000 PR#53 was merged, CI can now run oe-selftests, both pre- and post-build