From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 48903@debbugs.gnu.org
Subject: bug#48903: guix substitute: error: TLS error in procedure 'read_from_session_record_port': Error decoding the received TLS packet.
Date: Thu, 01 Jul 2021 15:12:11 +0200 [thread overview]
Message-ID: <874kdemb4k.fsf@gnu.org> (raw)
In-Reply-To: <871r8j5nev.fsf@gmail.com> (Maxim Cournoyer's message of "Wed, 30 Jun 2021 12:26:32 -0400")
Hi,
Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
> I've tried with the following modified version which runs multiple
> threads in parallel (to mimic --max-jobs=4 on the daemon), and I've yet
> to trigger it, although the hard drive is grinding heavily:
Note that ‘--max-jobs=4’ leads guix-daemon to spawn 4 ‘guix substitute’
processes, which is not what the script is doing here.
Are the other conditions the same, for instance same network, etc.?
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-07-01 13:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 15:10 bug#48903: guix substitute: error: TLS error in procedure 'read_from_session_record_port': Error decoding the received TLS packet Maxim Cournoyer
2021-06-07 17:46 ` Maxime Devos
2021-06-11 15:09 ` Ludovic Courtès
2021-06-20 11:07 ` bug#49132: guix substitute: backtrace when the network is disabled during substitution Maxime Devos
2021-06-22 14:06 ` Ludovic Courtès
2023-06-08 21:17 ` Maxime Devos
2021-06-29 13:23 ` bug#48903: guix substitute: error: TLS error in procedure 'read_from_session_record_port': Error decoding the received TLS packet Maxim Cournoyer
2021-06-29 21:18 ` Ludovic Courtès
2021-06-30 16:26 ` Maxim Cournoyer
2021-07-01 13:12 ` Ludovic Courtès [this message]
2021-07-02 14:26 ` Maxim Cournoyer
2021-07-05 16:12 ` Ludovic Courtès
2021-07-08 13:59 ` Maxim Cournoyer
2021-07-10 10:20 ` Ludovic Courtès
2021-08-07 4:23 ` Maxim Cournoyer
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874kdemb4k.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=48903@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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/guix.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).