since the tests should be self-sufficient in their dependencies for images built prior testing, having a step prior the testing for bitbake core-image-minimal makes no sense. Removing this step would improve the testing time for over half an hour and should have zero impact over the testing. If there are tests failing then those should be fixed to be self-sufficient.
M2 rc1 has been built, moving this to M3
We've seen multiple hangs when testing this change, it's clear there's more work to be done than just removing the BuildImage step. It's not yet clear what that work is.
This didn't make it for 2.3 M3, as it's an enhancement push to 2.4 M1
Only Failure was test_checkpkg (distrodata.Distrodata), which is known to be flaky.
morty builds fail with this change, they seem to require the BuildImages step have run before oe-selftest is invoked. I replicated this locally, with clean build directories and a checkout of the morty branch: i) invoking oe-selftest on the clean build directory results in the build being "stuck" at the "Running tests..." output of oe-selftest ii) building core-image-minimal in a clean build directory, then invoking oe-selftest things proceed as expected.
We'll achieve this by replacing the "core-image-minimal" BuildImages target with a placeholder value, for releases older than Pyro we'll replace the placeholder with core-image-minimal and for newer release we'll clear the placeholder.
Code and configuration changes made and waiting for idle period on the AB to deploy. http://git.yoctoproject.org/clean/cgit.cgi/yocto-autobuilder/commit/?id=086d06f1f3ae9d01d9987d6239676d01e220c64f http://git.yoctoproject.org/clean/cgit.cgi/yocto-autobuilder/commit/?id=eec3de41d07cc17cc776c726123e866aa54d13b8