From: 4ricci <4ricci@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: hitch: update to 1.7.0.
Date: Thu, 11 Mar 2021 20:10:29 +0100 [thread overview]
Message-ID: <20210311191029.Ve9lV0ppYc52tzbU12VC4uvsdPmH_4jZWGvwkZKydgw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29351@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 492 bytes --]
New comment by 4ricci on void-packages repository
https://github.com/void-linux/void-packages/pull/29351#issuecomment-796974853
Comment:
> It would appear that
>
> ```
> PASS: tests/test04-listen-with-own-certs.sh
> Error: The operation was canceled.
> ```
>
> is timing out?
Yes, looks like `tests/test05-multiple-listen-SNI.sh` is timing out on CI. Locally it passes just fine.
But on x86_64-musl `tests/test39-client-cert-proxy.sh` fails, I did not investigate the reason.
next prev parent reply other threads:[~2021-03-11 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29351@inbox.vuxu.org>
2021-03-11 18:05 ` ericonr
2021-03-11 19:10 ` 4ricci [this message]
2021-04-03 4:43 ` ericonr
2021-04-03 4:45 ` [PR PATCH] [Closed]: " ericonr
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=20210311191029.Ve9lV0ppYc52tzbU12VC4uvsdPmH_4jZWGvwkZKydgw@z \
--to=4ricci@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).