]> code.ossystems Code Review - openembedded-core.git/commit
oeqa/selftest: don't use cleanall in selftests
authorJoshua Lock <joshua.g.lock@intel.com>
Mon, 27 Mar 2017 10:21:32 +0000 (11:21 +0100)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Mon, 27 Mar 2017 19:22:43 +0000 (20:22 +0100)
commit9c948d3de08f158387e08a17cdc0cedc7d26bb54
tree64e7e702ba4c8e66bd93b5c2ee0f920933c94e10
parent4e6bf6ea766a0d47f96b3c4682d4f7e81a5763e7
oeqa/selftest: don't use cleanall in selftests

* devtool: oeqa.selftest.devtool.DevtoolTests is taking 4 or more hours on the
  autobuilder because the cleanall call deletes the tarball of the kernel
  source, forcing a large clone which is especially long on an NFS mount.

  The cleanall invocation isn't really required here and switching to clean
  instead should avoid hours of re-cloning the same repository each time we
  run oe-selftest on the autobuilder.
* buildoptions: We only need to ensure the first image isn't an incremental
  image, clean will suffice here.
* runtime-test: no need to clean up the artefacts generated during the test,
  let's leave that to a higher level process rather than using the cleanall
  hammer.

Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/lib/oeqa/selftest/buildoptions.py
meta/lib/oeqa/selftest/devtool.py
meta/lib/oeqa/selftest/runtime-test.py