From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-print/cups-browsed/
Date: Mon, 18 Dec 2023 03:54:10 +0000 (UTC) [thread overview]
Message-ID: <1702871604.fd6b80fed96eadee8e30f9d644f7a206143b1f7f.sam@gentoo> (raw)
commit: fd6b80fed96eadee8e30f9d644f7a206143b1f7f
Author: Eli Schwartz <eschwartz93 <AT> gmail <DOT> com>
AuthorDate: Sun Nov 12 21:38:24 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Dec 18 03:53:24 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fd6b80fe
net-print/cups-browsed: restrict tests
The tests are newly created during the 2.x upgrade. They will hang
forever if they cannot run properly. And running them properly has hit a
wall. I'm not sure where to go on from here.
Even getting this far means stepping outside of what portage can
reasonably require. Avahi only runs as root, and doesn't seem to have a
mocking mode, and even if it is running, the sandbox prevents src_test
from seeing it.
Signed-off-by: Eli Schwartz <eschwartz93 <AT> gmail.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>
net-print/cups-browsed/cups-browsed-2.0.0.ebuild | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/net-print/cups-browsed/cups-browsed-2.0.0.ebuild b/net-print/cups-browsed/cups-browsed-2.0.0.ebuild
index 6baeb697f2cd..0232d57c8b51 100644
--- a/net-print/cups-browsed/cups-browsed-2.0.0.ebuild
+++ b/net-print/cups-browsed/cups-browsed-2.0.0.ebuild
@@ -29,6 +29,18 @@ BDEPEND="
virtual/pkgconfig
"
+# The tests are new since the split out of cups-filters. Actually running them
+# seems to be challenging. You need:
+# - cups tools that are USE-optional
+# - running avahi-daemon (as root!)
+# - disable portage's pid-sandbox, which interferes with avahi
+# - ipptool still fails to connect to port 8xxx
+#
+# If anything fails, a `while true` loop fails to successfully launch and break
+# out of the loop, leading to a hang. Until there's an obvious recipe for
+# successfully running the tests, restrict it.
+RESTRICT="test"
+
PATCHES=(
"${FILESDIR}"/0001-cups-browsed.c-Fix-build-with-avahi-disabled-20.patch
)
@@ -47,6 +59,13 @@ src_configure() {
econf "${myeconfargs[@]}"
}
+src_test() {
+ # Requires avahi running. Hangs forever if not available.
+ avahi-daemon --check 2>/dev/null || die "no running avahi daemon found, cannot run tests"
+
+ default
+}
+
src_install() {
default
next reply other threads:[~2023-12-18 3:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 3:54 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-19 5:19 [gentoo-commits] repo/gentoo:master commit in: net-print/cups-browsed/ Sam James
2023-12-22 13:24 Mart Raudsepp
2023-12-29 14:36 Arthur Zamarin
2023-12-29 14:54 Arthur Zamarin
2023-12-29 14:55 Arthur Zamarin
2023-12-29 14:55 Arthur Zamarin
2023-12-30 1:26 Ionen Wolkens
2023-12-30 1:26 Ionen Wolkens
2024-01-03 8:41 Jakov Smolić
2024-01-25 1:05 Ionen Wolkens
2024-02-05 15:12 Sam James
2024-02-05 15:12 Sam James
2024-02-05 15:12 Sam James
2024-02-05 15:12 Sam James
2024-02-05 16:46 Sam James
2024-02-05 16:46 Sam James
2024-02-22 4:45 Ionen Wolkens
2024-09-26 21:21 Sam James
2024-09-27 5:30 Arthur Zamarin
2024-09-27 5:46 Arthur Zamarin
2024-09-28 13:33 Arthur Zamarin
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=1702871604.fd6b80fed96eadee8e30f9d644f7a206143b1f7f.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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