public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Ondrej Mosnacek <omosnace@redhat.com>
To: git-commits@fedoraproject.org
Subject: [tests/selinux] pr775-checkpolicy-revdeps: selinux-testsuite: do not check kernel RPM
Date: Fri, 11 Sep 2026 13:17:41 GMT	[thread overview]
Message-ID: <178913266173.1.154776747998899020.tests-selinux-221a043be0fd@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : tests/selinux
            Branch : pr775-checkpolicy-revdeps
            Commit : 221a043be0fd9fb974207ebe5d91d2152a07f953
            Author : Ondrej Mosnacek <omosnace@redhat.com>
            Date   : 2019-12-22T15:16:41+01:00
            Stats  : +0/-1 in 1 file(s)
            URL    : https://src.fedoraproject.org/tests/selinux/c/221a043be0fd9fb974207ebe5d91d2152a07f953?branch=pr775-checkpolicy-revdeps

            Log:
            selinux-testsuite: do not check kernel RPM

The RPM is not important, what is important is the running kernel (and
that can't be missing, obviously) and its version is already shown
elsewhere.

Moe importantly, in Fedora CI the 'kernel' RPM may not even be there, so
the test would warn about it, causing failures.

Reported-by: Lukas Vrabec <lvrabec@redhat.com>
Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>

---
diff --git a/kernel/selinux-testsuite/runtest.sh b/kernel/selinux-testsuite/runtest.sh
index 4b8acdc..422ac1f 100755
--- a/kernel/selinux-testsuite/runtest.sh
+++ b/kernel/selinux-testsuite/runtest.sh
@@ -189,7 +189,6 @@ rlJournalStart
     rlPhaseStartSetup
         rlAssertRpm ${PACKAGE}
         rlAssertRpm audit
-        rlAssertRpm kernel
         rlFileBackup /etc/selinux/semanage.conf
         # running the testsuite in /tmp causes permission denied messages
         # rlRun "TmpDir=\$(mktemp -d)" 0 "Creating tmp directory"

                 reply	other threads:[~2026-09-11 13:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178913266173.1.154776747998899020.tests-selinux-221a043be0fd@fedoraproject.org \
    --to=omosnace@redhat.com \
    --cc=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox