Hi Jakub, On 04/09/2026 20:51, Jakub Kicinski wrote: > On Fri, 4 Sep 2026 20:20:44 +0200 Matthieu Baerts wrote: >> These patches didn't get picked up in the tests because the Clang build >> failed with Rust code: >> >> https://netdev-ctrl.bots.linux.dev/logs/build/1158213/14791779/build_clang/stderr >> >> I only modified the selftests here. Other patches sent before me have >> the same issue, but some sent after don't. One of those "random" issues >> on the build server? > > kbuild / tools build likes to sometimes pick up the wrong source tree > if you have a worktree nested inside a git repo :/ > Here the Rust build was partially using the sources from the main repo > and partially from the work tree. > I'll push a NIPA workaround to sync the main repo to something recent > it should paper over this bug. It's not the first time it happened.
Thank you for the explanation, and for the fix! I was checking if I had to resend this series for the CI, but it looks like these patches have been taken by the "brancher" service, e.g. - https://github.com/linux-netdev/testing/commit/93408c0627c0 - https://github.com/linux-netdev/testing/commit/82fe019a07b0 Maybe they are there after the few hickups due to PW's update? (It is not clear why it says there is a conflict, but I guess that's because the contest job didn't override the status for the same reasons.) Anyway, no need to re-send them then. Or should I? Cheers, Matt
