On Sat, Dec 19, 2020 at 6:12 AM Ondrej Mosnacek <omosnace@xxxxxxxxxx> wrote: > On Thu, Dec 17, 2020 at 10:38 PM <paul@xxxxxxxxxxxxxx> wrote: > > > > SYSTEM: test-rawhide-1.lan > > DATE: Thu, 17 Dec 2020 16:38:34 -0500 > > > > KERNEL: Linux 5.11.0-0.rc0.20201217gite994cc240a3b.102.1.secnext.fc34.x86_64 > > > > audit-testsuite: PASS > > selinux-testsuite: FAILED ... > > ### START SELINUX TEST LOG > > Compiling targeted test_policy module > > Creating targeted test_policy.pp policy package > > domain_fd_use --> on > > Running as user root with context unconfined_u:unconfined_r:unconfined_t > > > > domain_trans/test ........... ok ... > > tun_tap/test ................ ok > > > > # Failed test at perf_event/test line 61. > > # Looks like you failed 1 test of 9. > > perf_event/test ............. > > Dubious, test returned 1 (wstat 256, 0x100) > > Failed 1/9 subtests > > So as you can see, we finally added the perf_event class to Fedora > policy :) (at least that one for a start...) > > The failure seems to be caused by the introduction of CAP_PERFMON (and > the fact that we haven't yet added *that one* to the policy...). I'll > try to come up with a patch, but it probably won't happen until next > year, so if someone wants to have a go at it, they are of course free > to do so :) Thanks for looking into this. I noticed some consistent test failures last week but figured I would give it a few days to see if it resolved upstream (test failures during the merge window are not uncommon, and they often resolve themselves in a day or two). At the very least I'll see if there is a quick patch I can do for my automated test runs so we don't keep seeing this failure. -- paul moore www.paul-moore.com
