The 'Recipe details' tab of the recipe details page includes a table listing all the tasks ran for the selected recipe. Right now, that table is showing _setscene tasks. _setscene tasks never display by themselves in Toaster: they are merged with their corresponding Cached task when they succeed, and with their corresponding executed task when they fail. _setscene tasks don't have an order number, so I guess we just need to check for any tasks with no order number and make sure they don't show in the tasks table of the recipe details page. toaster/master:213fef6e87cbf60d773e28d31653e3c626d4058e
Hi Belen, Can you describe the circumstance where "*_setscene tasks" may occur? I have a fresh build (no cache) and a duplicate build (100% cache) for "core-image-minimal", and neither have any such tasks, nor are there any task entries without order numbers (unless something is already filtering them out). - David
(In reply to comment #1) > Hi Belen, > > Can you describe the circumstance where "*_setscene tasks" may occur? _setscene tasks occur for any builds that reuse sstate objects, i.e. builds which include tasks with outcome Cached. For each Cached task there is a corresponding _setscene task with the same name as the Cached task, just adding _setscene at the end. _setscene tasks do not have an order number. To get a build with _setscene / Cached tasks, after you run a clean build, delete your /build/tmp directory. Then rebuild the same target. I hope this helps. Cheers Belén > > I have a fresh build (no cache) and a duplicate build (100% cache) for > "core-image-minimal", and neither have any such tasks, nor are there any > task entries without order numbers (unless something is already filtering > them out). > > - David
Waiting for merge.
commit 6f5e196d0f28be421f90b14bb0f2909cc9b6b275
verified in master:39846ddbce87d26eb68870914bf86a8ce5e86e5c