From: "Ludovic Courtès" <ludo@gnu.org>
To: Mikael Djurfeldt <mikael@djurfeldt.com>
Cc: 40125@debbugs.gnu.org
Subject: bug#40125: Problem with guix offload: Remote channel closed
Date: Sun, 22 Mar 2020 21:45:57 +0100 [thread overview]
Message-ID: <8736a0uni2.fsf@gnu.org> (raw)
In-Reply-To: <CAA2XvwJYu9rdZPOCTO54a4aLHFt8LngoDxtAVc151AnEcanjEw@mail.gmail.com> (Mikael Djurfeldt's message of "Sun, 22 Mar 2020 19:21:02 +0100")
Hello!
Mikael Djurfeldt <mikael@djurfeldt.com> skribis:
> This error message is more common. In this case, I couldn't see anything
> obviously strange except the following backtrace which contains strange
> characters:
>
> 31963 write(2, "Backtrace:\n 13 (apply-smob/1 #<catch-closure
> 56464c2232a0>)\nIn ice-9/boot-9.scm:\n 718:2 12 (call-with-prompt
> (\"prompt\") #<procedure 56464c2407e0 \342\200\246> \342\200\246)\nIn
> ice-9/eval.scm:\n 619:8 11 (_ #(#(#<directory (guile-user)
> 56464c2c4750>)))\nIn ice-9/command-line.scm:\n 181:18 10 (_ #<input:
> string 56464c2d2bd0>)\nIn unknown file:\n 9 (eval (begin
> (use-modules (guix) (srfi srfi-34) # #) \342\200\246) #)\nIn
> ice-9/eval.scm:\n 721:20 8 (primitive-eval (begin (use-modules (guix)
> (srfi \342\200\246) \342"..., 1150 <unfinished ...>
We’re missing a tiny bit. :-) Could you run strace with ‘-s 3000’ or
similar so that it doesn’t truncate it?
(The “strange characters” are Unicode HORIZONTAL ELLIPSIS.)
> I have also noticed that the above (the error message) happens inside the
> function send-files. It is the last error clause at the end of the function
> which reports the error message.
>
> I'd like to be able to, e.g., modify the function send-files to give some
> debugging output. How can I easily do that? Should I checkout guix with git
> and try to run it in the source tree? Or do you have other suggestions?
Note that the problems happens on the remote machine, which is what
makes it harder to debug.
If you want to debug (guix ssh), you’ll then have to run the daemon from
your Git checkout to exercise that code:
sudo -E ./pre-inst-env guix-daemon --build-users-group=guixbuild
HTH!
Ludo’.
next prev parent reply other threads:[~2020-03-22 20:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 19:58 bug#40125: Problem with guix offload: Remote channel closed Mikael Djurfeldt
2020-03-18 20:01 ` Mikael Djurfeldt
2020-03-21 15:50 ` Ludovic Courtès
2020-03-21 16:05 ` Mikael Djurfeldt
2020-03-21 20:00 ` Mikael Djurfeldt
2020-03-21 22:16 ` Ludovic Courtès
2020-03-22 18:21 ` Mikael Djurfeldt
2020-03-22 20:45 ` Ludovic Courtès [this message]
2020-03-22 21:40 ` Mikael Djurfeldt
2020-03-22 21:56 ` Mikael Djurfeldt
2020-03-22 22:13 ` Mikael Djurfeldt
2020-03-22 22:14 ` Mikael Djurfeldt
2020-03-22 22:24 ` Mikael Djurfeldt
2020-03-22 22:30 ` Marius Bakke
2020-03-22 22:44 ` Mikael Djurfeldt
2020-03-22 22:58 ` Marius Bakke
2020-03-22 23:12 ` Mikael Djurfeldt
2020-03-22 23:28 ` Mikael Djurfeldt
2020-03-22 23:40 ` Marius Bakke
2020-03-23 9:50 ` Ludovic Courtès
2023-08-02 15:09 ` 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=8736a0uni2.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=40125@debbugs.gnu.org \
--cc=mikael@djurfeldt.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).