On Mon, 2017-11-13 at 10:17 -0800, leonardo.sandoval.gonza...@linux.intel.com wrote: > From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> > > The main idea is to isolate the oe-selftest execution so neither the > current build dir nor the configuration data is touch/polluted. This > approach uses a wrapper script (which is the one presented on this > commit) which creates a unique directory and inside it copies all > scripts and metadata, re-initializes the enviroment (re-sources oe- > init-build-env) and finally launches the oe-selftest-internal (which > used to be oe-selftest) command, passing command arguments to the > latter.
This mode of operation may or may not be desirable. Can it be made optional? In refkit CI testing, several selftests run tests on build artifacts (primarily the images) produced during the previous build and only build them if needed, i.e. they run "bitbake some-image" and that is usually fast because the image already exists. Reusing sstate and download dir also is important for speed. Forcing all tests to run in a clean environment would make the overall CI run slower. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
