allow silencing feature test errors about ebpf

[lmb]

Originally posted by @ti-mo in #812 (comment)

[...] Build tags are a hard nack from me, and ldflags are quite cumbersome to specify.

We've also recently adopted envs in cilium/cilium to gate test behaviours. All in all, I think it's the lesser evil, because they can be set ambiently and are easy to slap onto any command, as there might be arbitrary tools/scripts in between your shell and the actual test binaries reading the env.

I'd probably go with a single env here (like EBPF_TEST_IGNORE_KERNEL_VERSION?) that basically trusts the verdict of our haveBPFXYZ() functions and doesn't execute the kernel version check. We could add this kind of skip in testutils.CheckFeatureTest() or testutils.checkKernelVersion(), although the latter might cause more unintended side effects.

As long as the default doesn't change and we don't relax CI.

[abhipranay]

@lmb I would like to work on this improvement.

I also feel testutils.CheckFeatureTest is better place to make this change.
How about keeping EBPF_TEST_IGNORE_KERNEL_VERSION as list of feature names ( snake cased + lowercase ) to ignore so that multiple features can be silenced.
eg: EBPF_TEST_IGNORE_KERNEL_VERSION="bpf_link_kprobe_multi,socket_filter".

[lmb]

Hey, thanks for taking some time to work on this!

Changing CheckFeatureTest sounds good to me, as does splitting on ,. Why do you want to use the feature name though? I think it would be easier to compare against tb.Name(), so that you could do EBPF_TEST_IGNORE_KERNEL_VERSION=TestHaveBatchAPI,TestHaveObjName. That way you can just copy and paste from the go test output if necessary.