From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: meta@public-inbox.org
Subject: t/pop3d.t failure on 1.9.0
Date: Wed, 21 Sep 2022 17:47:41 +0200 [thread overview]
Message-ID: <20220921154741.siubptwcv4463w5l@pengutronix.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
Hello,
I'm looking into packaging public-inbox 1.9.0 for Debian and stumble
over:
$ prove t/pop3d.t
t/pop3d.t .. skipped: certs/ missing for t/pop3d.t, run /usr/bin/perl ./create-certs.perl in certs/
Test Summary Report
-------------------
t/pop3d.t (Wstat: 0 Tests: 2 Failed: 0)
Parse errors: Bad plan. You planned 0 tests but ran 2.
Files=1, Tests=2, 0 wallclock secs ( 0.02 usr 0.00 sys + 0.17 cusr 0.02 csys = 0.21 CPU)
Result: FAIL
It looks better after I called the create-certs script, but IMHO it
should work as is and just skip the two tests as advertised?
After calling the create-certs script I get:
t/pop3d.t .. 1/? Not enough arguments for PublicInbox::Daemon::run at blib/script/public-inbox-pop3d line 8, near "'pop3://0.0.0.0:110')"
Execution of blib/script/public-inbox-pop3d aborted due to compilation errors.
Then it hangs. I'm not fluent enough in Perl to fix that quickly myself
and my today's time to look into public-inbox is running out, so I
thought I let you know.
Also happens on master.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-09-21 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 15:47 Uwe Kleine-König [this message]
2022-09-21 17:02 ` [PATCH] t/pop3d: skip all tests if no certs are found Eric Wong
2022-09-21 17:46 ` Uwe Kleine-König
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220921154741.siubptwcv4463w5l@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=meta@public-inbox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).