-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[test] test in actuated runners #219
Conversation
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Fix the following gosec warnings in tests by using uint32 everywhere, so we don't have to do a single cast: pkg/pwalk/pwalk_test.go:29:20: G115: integer overflow conversion int -> uint32 (gosec) if count != uint32(total) { ^ pkg/pwalk/pwalk_test.go:73:15: G115: integer overflow conversion int -> uint32 (gosec) max := uint32(total / 2) ^ pkg/pwalk/pwalk_test.go:86:21: G115: integer overflow conversion int -> uint32 (gosec) if count != uint32(total) { ^ pkg/pwalkdir/pwalkdir_test.go:32:20: G115: integer overflow conversion int -> uint32 (gosec) if count != uint32(total) { ^ pkg/pwalkdir/pwalkdir_test.go:76:15: G115: integer overflow conversion int -> uint32 (gosec) max := uint32(total / 2) ^ pkg/pwalkdir/pwalkdir_test.go:89:21: G115: integer overflow conversion int -> uint32 (gosec) if count != uint32(total) { ^ While at it, - switch from atomic op (atomic.AddUint32) to atomic type (atomic.Int32) with methods, which is more error-prone; - rename max to maxFiles as the former is now a built-in function. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Currently supported go versions are 1.22 and 1.23. Drop min and max functions now, as Go 1.21 has built-in ones. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Most of parseLevelItem users will cast its result to int. On a 32-bit platform this means we may end up with a negative number. So, let's limit bitSize to 31 in a call to ParseUint, and return int so there are less typecasts in the code. Also, change MLS level to use int, for the same reason (less typecasts). This fixes the following gosec warnings: go-selinux/selinux_linux.go:505:30: G115: integer overflow conversion uint -> int (gosec) bitset.SetBit(bitset, int(i), 1) ^ go-selinux/selinux_linux.go:512:29: G115: integer overflow conversion uint -> int (gosec) bitset.SetBit(bitset, int(cat), 1) ^ go-selinux/selinux_linux.go:626:31: G115: integer overflow conversion uint -> int (gosec) low := "s" + strconv.Itoa(int(m.low.sens)) ^ go-selinux/selinux_linux.go:635:32: G115: integer overflow conversion uint -> int (gosec) high := "s" + strconv.Itoa(int(m.high.sens)) ^ Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Gosec doesn't like this code: go-selinux/selinux_linux.go:141:11: G115: integer overflow conversion int64 -> uint32 (gosec) if uint32(buf.Type) != uint32(unix.SELINUX_MAGIC) { ^ But it is correct because - buf.Type is int64 or int32, depending on the platform; - unix.SELINUX_MAGIC is untyped int which overflows int32 (i.e. it becomes negative). So the best type to use here is uint32. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Gosec complains: go-selinux/selinux_linux.go:587:14: G115: integer overflow conversion uint -> int (gosec) for i := int(c.TrailingZeroBits()); i < c.BitLen(); i++ { ^ This is indeed a valid concern in case TrailingZeroBits returns a value which uses a highest bit (i.e. more than MaxInt32 or MaxInt64, depending on the platform). But I think this is highly unlikely. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
The new version produces the following warnings: WARN [config_reader] The configuration option `linters.govet.check-shadowing` is deprecated. Please enable `shadow` instead, if you are not using `enable-all`. WARN The linter 'exportloopref' is deprecated (since v1.60.2) due to: Since Go1.22 (loopvar) this linter is no longer relevant. Replaced by copyloopvar. so fix the configuration accordingly. Note we do not enable copyloopvar since it requires Go 1.22 and we're currently have it set to Go 1.21. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Since v5, golangci-lint-action relies on actions/setup-go for caching, so remove "cache: false" from actions/setup-go to re-enable caching. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
The sole reason is to simplify branch protection rules, requiring just this one to be passed. I tried but could not find a way to list all other jobs, so had to add all of them manually. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
401fac8
to
e2e6498
Compare
Managed to make it work, with a handful of failures:
@rhatdan can you take a look? (I've seen occasional errors from |
Actuated runners have Ubuntu with SELinux configured, so we can actually run the test cases here (most of which require SELinux enabled). Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Nevermind, [most of] the failures are caused by missing container-selinux (and thus things like |
Going with Cirrus CI instead, but I'm stuck as I don't have rights. |
(currently includes #218 but it's not really required here).