15824 2025-04-08 06:19:41 +0000 rm_work and populate_sdk 2026-04-15 19:15:02 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core unspecified x86 Multiple NEW Medium normal 6.1 1 sean unassigned antonin.godard meta.mr.watcher meta.watcher randy.macleod yoann.congal zhangle.yang --- --- Don't know oldest_to_newest 101582 0 sean 2025-04-08 06:19:41 +0000 When rm_work is enabled and when building an image it works as I would expect. But when running populate_sdk for that image, it doesn't look like it's running the rm_work task and the disk usage increases. I have tried adding [0] to my image recipe, and it makes a significant difference in disk usage. Some numbers for reference:: With sstate and without [0]: 26G build/ With sstate and with [0]: 18G build/ Without sstate and without [0]: 120G build/ Without sstate and with [0]: 29G build/ 101606 1 antonin.godard 2025-04-10 14:19:36 +0000 [0] was forgotten to be included: addtask do_populate_sdk_and_rmwork after do_populate_sdk do_populate_sdk_and_rmwork[recrdeptask] = "do_rm_work" From https://lists.openembedded.org/g/openembedded-core/message/214401. 105083 2 randy.macleod 2026-04-15 19:15:02 +0000 This looks like a nice simple bug fix / enhancement for 6.1.