public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Vit Mojzis <vmojzis@redhat.com>
To: git-commits@fedoraproject.org
Subject: [tests/selinux] pr775-checkpolicy-revdeps: libsemanage/verify-options-in-semanage-conf: Extend error messages
Date: Fri, 11 Sep 2026 13:23:04 GMT [thread overview]
Message-ID: <178913298493.1.11747352323178854267.tests-selinux-9948e7bcf02e@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : tests/selinux
Branch : pr775-checkpolicy-revdeps
Commit : 9948e7bcf02e2a3175b0a6329b90824243d56f9f
Author : Vit Mojzis <vmojzis@redhat.com>
Date : 2025-07-25T21:17:30+02:00
Stats : +4/-4 in 1 file(s)
URL : https://src.fedoraproject.org/tests/selinux/c/9948e7bcf02e2a3175b0a6329b90824243d56f9f?branch=pr775-checkpolicy-revdeps
Log:
libsemanage/verify-options-in-semanage-conf: Extend error messages
Userspace 3.9 changes the error message to "OSError: No data available".
Signed-off-by: Vit Mojzis <vmojzis@redhat.com>
---
diff --git a/libsemanage/verify-options-in-semanage-conf/runtest.sh b/libsemanage/verify-options-in-semanage-conf/runtest.sh
index d17ed44..c295509 100755
--- a/libsemanage/verify-options-in-semanage-conf/runtest.sh
+++ b/libsemanage/verify-options-in-semanage-conf/runtest.sh
@@ -61,7 +61,7 @@ rlJournalStart
rlAssertNotGrep "semodule.*failed" ${OUTPUT_FILE} -i
rlRun "semodule -l | grep ${MODULE_NAME}"
rlRun "semanage module -a ${MODULE_NAME}.pp 2>&1 | tee ${OUTPUT_FILE}"
- rlAssertNotGrep "could not commit semanage transaction|no such file or directory" ${OUTPUT_FILE} -Ei
+ rlAssertNotGrep "could not commit semanage transaction|no such file or directory|No data available" ${OUTPUT_FILE} -Ei
rlRun "semanage module -l | grep ${MODULE_NAME}"
rlPhaseEnd
@@ -73,7 +73,7 @@ rlJournalStart
rlAssertNotGrep "semodule.*failed" ${OUTPUT_FILE} -i
rlRun "semodule -l | grep ${MODULE_NAME}"
rlRun "semanage module -a ${MODULE_NAME}.pp 2>&1 | tee ${OUTPUT_FILE}"
- rlAssertNotGrep "could not commit semanage transaction|no such file or directory" ${OUTPUT_FILE} -Ei
+ rlAssertNotGrep "could not commit semanage transaction|no such file or directory|No data available" ${OUTPUT_FILE} -Ei
rlRun "semanage module -l | grep ${MODULE_NAME}"
rlPhaseEnd
@@ -102,7 +102,7 @@ rlJournalStart
rlAssertGrep "semodule.*failed" ${OUTPUT_FILE} -i
rlRun "semodule -l | grep ${MODULE_NAME}" 1
rlRun "semanage module -a ${MODULE_NAME}.pp 2>&1 | tee ${OUTPUT_FILE}"
- rlAssertGrep "could not commit semanage transaction|no such file or directory" ${OUTPUT_FILE} -Ei
+ rlAssertGrep "could not commit semanage transaction|no such file or directory|No data available" ${OUTPUT_FILE} -Ei
rlRun "semanage module -l | grep ${MODULE_NAME}" 1
rlPhaseEnd
@@ -114,7 +114,7 @@ rlJournalStart
rlAssertGrep "semodule.*failed" ${OUTPUT_FILE} -i
rlRun "semodule -l | grep ${MODULE_NAME}" 1
rlRun "semanage module -a ${MODULE_NAME}.pp 2>&1 | tee ${OUTPUT_FILE}"
- rlAssertGrep "could not commit semanage transaction|no such file or directory" ${OUTPUT_FILE} -Ei
+ rlAssertGrep "could not commit semanage transaction|no such file or directory|No data available" ${OUTPUT_FILE} -Ei
rlRun "semanage module -l | grep ${MODULE_NAME}" 1
rlPhaseEnd
reply other threads:[~2026-09-11 13:23 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=178913298493.1.11747352323178854267.tests-selinux-9948e7bcf02e@fedoraproject.org \
--to=vmojzis@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