avoid having to run the 'go' compiler with sudo in 'make test' about tetragon

[kkourt]

Maybe something like the following:

for pkg in $(go list ./...)
do
   localpkg=$(echo $pkg | sed -e 's:github.com/cilium/tetragon/::')
   localtestfile=$(echo $localpkg | sed -e 's:/:.:g')
   echo go test -c ./$localpkg -o go-tests/$localtestfile
done

[willfindlay]

Are these all or only some? We should build all test binaries like this in a step other than make test (that one would run with sudo), maybe just in make itself or one of its dependencies.

Right, it's non-exhaustive at the moment. I think the "right" way to do this would probably be with a glob in the Makefile that compiles all tests (rather than hard-coding each one which, as you've pointed out is very error-prone as new tests are added). Then we would have another target as you suggest that would run each test (also using a glob).

A PR would be much appreciated!

[kkourt]

We should build the test binaries with go test -c in a make step that doesn't require 'sudo', and then only run those test binaries with sudo.

That would be great!
We can even support both options and keep the one above for the people that want it.

Are these all or only some? We should build all test binaries like this in a step other than make test (that one would run with sudo), maybe just in make itself or one of its dependencies.

I don't think that's all. I think a better approach would be to use go list ./... to get all the packages, and then (somehow) build the proper binaries.

[kkourt]

Above ☝🏼 exists now (test-compile target), so closing this.