From: Christopher Baines <mail@cbaines.net>
To: 62590@debbugs.gnu.org
Subject: bug#62590: Strange put-char encoding-error "conversion to port encoding failed"
Date: Sat, 01 Apr 2023 12:37:16 +0100 [thread overview]
Message-ID: <87cz4nn7zw.fsf@cbaines.net> (raw)
Hey,
I've been seeing some strange occasional errors for a while now.
Here are some log messages from the guix-build-coordinator:
worker-thread: exception: (encoding-error put-char conversion to port encoding failed 84 #<output: file 1> s)
encoding-error (put-char conversion to port encoding failed 84 #<output: file 1> s)
encoding-error (put-char conversion to port encoding failed 84 #<output: file 1> w)
encoding-error (put-char conversion to port encoding failed
84 #<output: file 1> 2
encoding-error (put-char conversion to port encoding fencoding-error (put-char conversion to port encoding failed 84 #<o
utput: file 1> w)
encoding-error (put-char conversion to port encoding failed 84 #<output: file 1> w)
2022-10-02 17:23:38 (ERROR): error running build-success hook: encoding-error (put-char conversion to port encoding failed
84 #<output: file 1> B)
Throw to key `encoding-error' with args `("put-char" "conversion to port encoding failed" 84 #<output: file 1> #\p)'.
2022-10-02 21:21:37 (ERROR): error running build-success hook: misc-error (#f ~A (error: command failed (1): (/gnu/store/6
Throw to key `encoding-error' with args `("put-char" "conversion to port encoding failed" 84 #<output: file 1> #\space)'.
Throw to key `encoding-error' with args `("put-char" "conversion to port encoding failed" 84 #<output:
file 1> #\2)'.
I'm not sure what the 84 means? If I'm picking out the characters that
have failed to be encoded, I'm not sure why some of these would fail
(like space or w)?
Unfortunately I'm not sure how to reproduce this. Suspendable ports
might be a factor here as that is probably in use.
next reply other threads:[~2023-04-01 11:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 11:37 Christopher Baines [this message]
2024-01-21 4:01 ` bug#62590: Strange put-char encoding-error "conversion to port encoding failed" Felix Lechner via Bug reports for GUILE, GNU's Ubiquitous Extension Language
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cz4nn7zw.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=62590@debbugs.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).