For export test, we'd like to have test tar balls with only simple runner, controller and test cases. No need to include build information and build tools in it.
Hi Cathy, To be clear, the way tests with binaries (both native and DUT specific) are exported now is by creating a self extracting tarball that contains two main parts: 1) the buildtools related files used to ensure the remote machine that will launch tests on DUT has everything needed for an SDK, allowing anyone to develop applications for the DUT. It also includes any needed native binaries (inside sysroots directory) 2) the tests related part, composed of exported_binaries directory that contains the necessary binaries for DUT only and the exported_tests directory that contains the runexported.py script + all .py test files. You would like to have "1)" removed and not care of any remote machine files? Also you would like the resulting files associated to "2)" to be included in a tarball (not self extracting tarball as it is now and possibility to install it like: cd / tar -xvzf tarball_name.tar.gz)? If so, it means the remote machine will have no possibility to offer SDK functionality Thank you. Costin
(In reply to comment #1) > 1) the buildtools related files used to ensure the remote machine that will > launch tests on DUT has everything needed for an SDK, allowing anyone to > develop applications for the DUT. It also includes any needed native > binaries (inside sysroots directory) For this item, we don't need SDK stuff in the test tar ball, which is useful for developing applications for DUT but not necessary for testing. Native test binaries are needed for this test tar ball. IoT still need SDK support from Yocto per my understanding, but it's another request. Let me know if it's clear enough. We can have a short meeting to go through these requirements if you have more questions.
Hi Cathy, It's clear enough. Thank you.
This should separate everything as desired. Please use latest hash http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=cc-tin/YP7850_final
Cathy, The idea behind export test is to decouple the tests from the build environment. I must admit this functionality breaks from time to time. Can you elaborate more in what is needed here? Thanks
To be simple, if the exported test tar ball can be deployed to another Linux machine w/o Yocto bitbake build environment and trigger the test successfully, it means it's "decoupled" export test with Yocto build environment. @Jing, do you have more details on this requirement?
Given test suite is exported, it means *) it can be deployed to a new environment without poky build system for execution *) It should be lightweight, just include test suite and test runner *) Trigger testing from test runner directly, not bitbake.
Sent patches to the mailing list: http://lists.openembedded.org/pipermail/openembedded-core/2016-May/121992.html
This has been solved with commits: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=549f134970b0ba0ad06256d7514b4bea1419da27 http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=a9eb22e3d30b9bfd06eea55556894c256be3a4b0 http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=b3a656374b2fce0a1ac236fab80998ac5d3a1726