15569 2024-08-05 11:56:57 +0000 Add janitor support for handling failed builds 2026-04-02 15:10:55 +0000 1 1 5 Infrastructure AutoBuilder autobuilder unspecified x86 Multiple NEW Medium+ enhancement 6.1 M2 1 richard.purdie unassigned infras.ab.watcher Infras.watcher mhalstead pidge randy.macleod --- --- No (bug/feature does not impact docs) oldest_to_newest 99491 0 richard.purdie 2024-08-05 11:56:57 +0000 I've changed the code in autobuilder2: https://git.yoctoproject.org/yocto-autobuilder2/commit/?id=d809e29a23d5614d8873c3f5f1fb7293da96cdd0 which increases the space limit from 100G to 200G. I also added monitoring to /tmp since that caused a lot of build issues in a recent failure. This will help but I think we need to improve the janitor to clean up failed builds. I'm thinking of something like a queuing system so any build failure gets put into the queue and anything older gets deleted as soon as the system is under disk pressure? This would solve the issue that: * builds the rerun on the same worker destroy failed data immediately * older builds can build up and clog systems It would also make it easy to put a policy in place: * to immediately delete reproducible fails (for exmaple) * to delete builds when space drops to a threshold Help with this would be very welcome. Ideally we'd have a way via a UI to mark failed builds as not wanted but I'm not sure how to do right now. 99517 1 randy.macleod 2024-08-08 14:33:51 +0000 Likely got to be done in 5.2... 100799 2 randy.macleod 2025-01-30 16:06:38 +0000 Bulk move to 5.2-M3. 100814 3 randy.macleod 2025-01-30 16:17:04 +0000 Bulk move to 5.2-M3 and this time I'll actually specify M3! 104908 4 randy.macleod 2026-04-01 18:33:58 +0000 I doubt this has been done but leaving for bug review team to schedule.