From: zimoun <zimon.toutoune@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: 33463@debbugs.gnu.org
Subject: bug#33463: guix publish error on Hydra: fport_close: Bad file descriptor
Date: Thu, 16 Sep 2021 09:51:00 +0200 [thread overview]
Message-ID: <86mtodq7q3.fsf@gmail.com> (raw)
In-Reply-To: <878t1mrl2c.fsf@netris.org> (Mark H. Weaver's message of "Wed, 21 Nov 2018 19:51:12 -0500")
Hi Mark,
This old bug [1] is about Hydra which is down now, IIRC.
Does it make sense to keep it open? If yes, what could be the
actionable next step?
On Wed, 21 Nov 2018 at 19:51, Mark H Weaver <mhw@netris.org> wrote:
> FYI, I just spotted this output from "guix publish" on Hydra.
>
> Mark
>
>
> GET /sd34hpwkjdax611r4cqqk5rhna79sl9k.narinfo
> GET /ndbv402716xnhsy229m2mgx7lf415ank.narinfo
> GET /jj4ibyflqrd24xb16p7vsadj7nr3ik2k.narinfo
> GET /fxxba73sgq1r2vav5imj2wsp6cy4mqlj.narinfo
> GET /d38frkfi36nq10c0sss7fr8rnz2alhdn.narinfo
> GET /clgxxvd97r7dwgdx0vczwp90hhcixnvm.narinfo
> GET /bq2c0p4bl18fh0fbd0zav0svnry9c60x.narinfo
> In guix/workers.scm:
> GET /911rlhagn0f6rcwf6ysfjd0c3xvmi3cp.narinfo
> 74:9 2 (_)
> 78:32 1 (_ system-error "fport_close" "~A" ("Bad file descrip…") …)
> In unknown file:
> 0 (make-stack #t)
> ERROR: In procedure make-stack:
> ERROR: In procedure fport_close: Bad file descriptor
> GET /21fbk56f29242d246z79d11yv6bsayny.narinfo
> GET /mz2ysbhy69y90n6wcyjb1slpcacl08v1.narinfo
1: <http://issues.guix.gnu.org/issue/33463>
Thanks,
simon
next prev parent reply other threads:[~2021-09-16 7:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 0:51 bug#33463: guix publish error on Hydra: fport_close: Bad file descriptor Mark H Weaver
2021-09-16 7:51 ` zimoun [this message]
2021-09-16 8:15 ` Mark H Weaver
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=86mtodq7q3.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=33463@debbugs.gnu.org \
--cc=mhw@netris.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.