[poky] [PATCH] oeqa/selftest/systemd_boot: Never use cleansstate in QA tests without special handling of SSTATE_DIR

[Richard Purdie]

On Sun, 2018-07-15 at 20:29 +0100, Burton, Ross wrote:
> On 15 July 2018 at 16:17,  <poky-bounces at yoctoproject.org> wrote:
> > Removing things straight from the live sstate directory is prone to
> > issues
> > since other builds may be relying on the artefact presence.
> > 
> > Also, cleansstate is very slow on the huge sstate that the
> > autobuilder has
> > on slow NFS drives. This may well be causing long buildtimes in oe-
> > selftest
> > as the time taken to remove the artefact by be long.
> 
> Argh, I thought we vetted selftest for this sort of thing already.

This one was added in the last 12 months since its in sumo/rocko but
not before so we missed it :(.

> Does the test still do the right thing with this?  Several instances
> where it really wanted to build in the past I've replaced with
> bitbake foo -C unpack or similar.

As far as I can tell it wanted to ensure the item ends up deployed, in
which case the -c clean and then the build should be fine. Whether it
comes from sstate or not I'm not sure is relevant but I didn't look
really closely at the test.

Cheers,

Richard