On Fri, 12 Apr 2024 08:53:30 +0200 Florian Westphal wrote: > > Either tree works, FWIW. > > > > I presume we should add these to the netdev CI, right? > > After all scripts have been updated it would be great if you > could do that, yes. > > ATM too many nf tests barf for various reasons. > > > Assuming yes - I need to set up the worker manually. A bit of a chicken > > and an egg problem there. The TARGET must exist when I start it > > otherwise worker will fail :) These missed the > > net-next-2024-04-12--00-00 branch, I'll start the worker first thing in > > the morning.. > > Let me know how I can help. Alright, the workers are churning. For now I excluded this target from patchwork reporting, but they are running and showing up on the status page (in the ignored section). Looks like most of the tests skip: https://netdev.bots.linux.dev/contest.html?branch=net-next-2024-04-12--12-00&executor=vmksft-nf I looked at a few, they all said: # mnl_socket_open: Protocol not supported The resulting kernel config is here: https://netdev-3.bots.linux.dev/vmksft-nf/results/548802/config
