From: Lars Ingebrigtsen <larsi@gnus.org>
To: Ken Brown <kbrown@cornell.edu>
Cc: "Mattias Engdegård" <mattiase@acm.org>, 55858@debbugs.gnu.org
Subject: bug#55858: 28.1; process-async-https-with-delay failure
Date: Thu, 09 Jun 2022 15:07:32 +0200 [thread overview]
Message-ID: <87r13y56jv.fsf@gnus.org> (raw)
In-Reply-To: <7ab5acbf-67a7-2c78-b9d7-eab2d02c7972@cornell.edu> (Ken Brown's message of "Wed, 8 Jun 2022 18:04:05 -0400")
Ken Brown <kbrown@cornell.edu> writes:
> Second, I think it's a bug that the test is causing /nonexistent to be
> accessed. Maybe it would make more sense for the test to be skipped if
> the certificate can't be verified.
I'm not sure that test should be in our repertoire at all. We're pretty
strict about not "phoning home" (because of privacy concerns), and while
this is wholly innocuous in this case, it is surprising that saying
"make check" will inform the people running elpa.gnu.org that you're
doing so.
(And as a practical matter, bugs in external network connections/sites
shouldn't make a test fail.)
I think that test should be removed, or rewritten to be wholly local, so
I've added Mattias to the CC, since he added that test.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-06-09 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 22:04 bug#55858: 28.1; process-async-https-with-delay failure Ken Brown
2022-06-09 5:26 ` Eli Zaretskii
2022-06-09 8:30 ` Robert Pluim
2022-06-09 6:44 ` Achim Gratz
2022-06-09 11:17 ` Ken Brown
2022-06-09 13:07 ` Lars Ingebrigtsen [this message]
2022-07-11 11:20 ` Lars Ingebrigtsen
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r13y56jv.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=55858@debbugs.gnu.org \
--cc=kbrown@cornell.edu \
--cc=mattiase@acm.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://git.savannah.gnu.org/cgit/emacs.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).