As the logic in bitbake improves, the logic in the tests needs to as well.
Afer we built a task for the first time, allow its setscene hash verification
status to change, mirroring what would happen in a multiconfig build.
(Bitbake rev:
27ec2e69ab3e32972caf8b072b2945736696d83d)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
import time
thistask = d.expand("${PN}:${BB_CURRENTTASK}")
+ with open(d.expand("${TOPDIR}/%s.run") % thistask, "a+") as f:
+ f.write("\n")
+
if d.getVar("BB_CURRENT_MC") != "default":
thistask = d.expand("${BB_CURRENT_MC}:${PN}:${BB_CURRENTTASK}")
if thistask in d.getVar("SLOWTASKS").split():
if n in valid:
bb.note("SState: Found valid sstate for %s" % n)
ret.append(task)
+ elif os.path.exists(d.expand("${TOPDIR}/%s.run" % n.replace("do_", ""))):
+ bb.note("SState: Found valid sstate for %s (already run)" % n)
+ ret.append(task)
else:
missed.append(task)
bb.note("SState: Found no valid sstate for %s" % n)