public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Milos Malik <mmalik@redhat.com>
To: git-commits@fedoraproject.org
Subject: [tests/selinux] pr775-checkpolicy-revdeps: add missing metadata to the tests
Date: Fri, 11 Sep 2026 13:21:47 GMT [thread overview]
Message-ID: <178913290783.1.12460182014458330176.tests-selinux-3e4943c5966f@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : tests/selinux
Branch : pr775-checkpolicy-revdeps
Commit : 3e4943c5966f2bdfdfbbf203b9218c174de5f58c
Author : Milos Malik <mmalik@redhat.com>
Date : 2024-07-10T17:18:28+00:00
Stats : +8/-3 in 4 file(s)
URL : https://src.fedoraproject.org/tests/selinux/c/3e4943c5966f2bdfdfbbf203b9218c174de5f58c?branch=pr775-checkpolicy-revdeps
Log:
add missing metadata to the tests
Some tests were missing important TCMS metadata. Now, the problem
should be fixed.
---
diff --git a/libselinux/matchpathcon-in-chroot-env/main.fmf b/libselinux/matchpathcon-in-chroot-env/main.fmf
index edc58c1..d671bcf 100644
--- a/libselinux/matchpathcon-in-chroot-env/main.fmf
+++ b/libselinux/matchpathcon-in-chroot-env/main.fmf
@@ -24,4 +24,5 @@ link:
- verifies: https://issues.redhat.com/browse/RHEL-46558
extra-summary: /CoreOS/libselinux/Regression/matchpathcon-in-chroot-env
extra-task: /CoreOS/libselinux/Regression/matchpathcon-in-chroot-env
-
+extra-nitrate: TC#0617627
+id: 649c1bfa-1739-4d87-8799-f37fd30499f4
diff --git a/libselinux/setfiles-in-chroot-env/main.fmf b/libselinux/setfiles-in-chroot-env/main.fmf
index b5a9ced..9c3dae5 100644
--- a/libselinux/setfiles-in-chroot-env/main.fmf
+++ b/libselinux/setfiles-in-chroot-env/main.fmf
@@ -19,4 +19,4 @@ link:
- verifies: https://bugzilla.redhat.com/show_bug.cgi?id=2094683
extra-summary: /CoreOS/libselinux/Regression/setfiles-in-chroot-env
extra-task: /CoreOS/libselinux/Regression/setfiles-in-chroot-env
-
+extra-nitrate: TC#0613958
diff --git a/libselinux/setfiles-in-chroot-env/runtest.sh b/libselinux/setfiles-in-chroot-env/runtest.sh
index d9afeb2..0dfb100 100755
--- a/libselinux/setfiles-in-chroot-env/runtest.sh
+++ b/libselinux/setfiles-in-chroot-env/runtest.sh
@@ -30,6 +30,9 @@
PACKAGE="libselinux"
CHROOT_DIR=`mktemp -d`
+if rlIsFedora ; then
+ INSTALL_OPTION="--use-host-config"
+fi
rlJournalStart
rlPhaseStartSetup
@@ -38,7 +41,7 @@ rlJournalStart
rlPhaseEnd
rlPhaseStartTest "bz#2094683"
- rlRun "yum -y install filesystem policycoreutils selinux-policy-targeted --installroot=${CHROOT_DIR} --disablerepo 'epel*'"
+ rlRun "yum -y install filesystem policycoreutils selinux-policy-targeted --installroot=${CHROOT_DIR} ${INSTALL_OPTION}"
rlRun "cp ./test-script.sh ${CHROOT_DIR}/usr/bin/"
rlRun -s "chroot ${CHROOT_DIR} /usr/bin/test-script.sh"
rlRun "grep -i -e 'no such file or directory' -e 'not set context' $rlRun_LOG" 1
diff --git a/policycoreutils/sctp_test/main.fmf b/policycoreutils/sctp_test/main.fmf
index c82f8da..9b5ed69 100644
--- a/policycoreutils/sctp_test/main.fmf
+++ b/policycoreutils/sctp_test/main.fmf
@@ -14,3 +14,4 @@ link:
- relates: https://bugzilla.redhat.com/show_bug.cgi?id=1770238
extra-summary: /selinux/policycoreutils/sctp_test
extra-task: /selinux/policycoreutils/sctp_test
+extra-nitrate: TC#0614834
reply other threads:[~2026-09-11 13:21 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=178913290783.1.12460182014458330176.tests-selinux-3e4943c5966f@fedoraproject.org \
--to=mmalik@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