Igor

Oh, that is unfortunate and doesn't seems like a trivial problem :( See this: https://github.com/armbian/build/blob/main/config/sources/families/rk35xx.conf linux-image-legacy-rk33xx would at least not make any conflicts. And leave / add / try also...

> Might be related to some improper cleanup It is possible this was produced by us in past several months.

This hasn't been seen for awhile.

> On ubuntu-22.04 all build target done, but 1 bpi-f3 fail yes > On ubuntu-24.04 12 target fail yes

There are several others: https://github.com/armbian/os/actions/runs/9769962830/attempts/5


Now we need to move to Noble. I will start to disable those that doesn't build. 

Some weird devices that are not actively monitored probably still have problems, but those we won't be fixing anyway. I think we can close this down.

Some build steps are I/O or wait-bound. It helps keep all cores busy when some jobs are waiting. Rule of thumb: make -j$(nproc * 1.5). We have been using this...

> is that the desired changes should first be made and tested in mainline armbian/build and then backported to the release branch (24.5 in this case) Agree. What to do...