Re: [bitbake-devel] [PATCH RFC 3/3] runqueue: Hand each covered task's log to a single setscene task

["Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>]

On Sun Oct 25, 2026 at 3:20 PM CET, Richard Purdie wrote:
> On Sat, 2026-10-24 at 14:33 +0200, Mathieu Dubois-Briand via lists.openembedded.org wrote:
>> When a setscene task starts, hand it the covered tasks of the same recipe
>> which were not yet handed to another setscene task, and pass their names
>> to the task through BB_SETSCENE_REPLAY_TASKS. Several setscene tasks can
>> cover the same task (e.g. do_populate_sysroot and do_package both cover
>> do_compile), so this lets metadata replay the log of each covered task
>> exactly once when restoring it from the sstate cache.
>> 
>> AI-Generated: Uses opencode (DeepSeek V4 Flash)
>> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
>> ---
>>  bin/bitbake-worker | 1 +
>>  lib/bb/runqueue.py | 9 +++++++++
>>  2 files changed, 10 insertions(+)
>
> This is a very specific piece of API, specifically tailored to what
> this particular task entails.
>

Just to make sure I fully understand this: I should rather try to rely
more on existing API or introduce something a bit more generic. Is that
right?

> I'm a bit worried that it still doesn't cover everything it should, for
> example a warning from another recipe that is only covered by a given
> sstate task and nothing else.

Indeed. Knowing we have to replay these logs should be easy, but
accessing these logs in the first place might be a bit tricky. I will
have to experiment a bit and understand what is possible.

>
> You can pobably calculate it from BB_TASKDEPDATA already too, if you
> know which tasks are sstate, which I think we know.
>
> There is also the potential for multiple log output from these covered
> tasks, e.g. do_package and do_populate_sysroot both 'cover' on
> do_install so a warning from do_install will be shown by both tasks at
> setscene time.
>

This should not happen with the current code. But I will have to be
careful when covering tasks from another recipe.

In your example, only one of the two tasks should be assigned with the
logs of do_install, either do_package or do_populate_sysroot, but not
both. This is the point of the sq_replay_assigned set here.

Also, it should be covered by my tests on the oe-core side.

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com