bug#33463: guix publish error on Hydra: fport

unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed

* bug#33463: guix publish error on Hydra: fport_close: Bad file descriptor
@ 2018-11-22  0:51 Mark H Weaver
  2021-09-16  7:51 ` zimoun
  0 siblings, 1 reply; 3+ messages in thread
From: Mark H Weaver @ 2018-11-22  0:51 UTC (permalink / raw)
  To: 33463

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* bug#33463: guix publish error on Hydra: fport_close: Bad file descriptor
  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
  2021-09-16  8:15   ` Mark H Weaver
  0 siblings, 1 reply; 3+ messages in thread
From: zimoun @ 2021-09-16  7:51 UTC (permalink / raw)
  To: Mark H Weaver; +Cc: 33463

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




^ permalink raw reply	[flat|nested] 3+ messages in thread

* bug#33463: guix publish error on Hydra: fport_close: Bad file descriptor
  2021-09-16  7:51 ` zimoun
@ 2021-09-16  8:15   ` Mark H Weaver
  0 siblings, 0 replies; 3+ messages in thread
From: Mark H Weaver @ 2021-09-16  8:15 UTC (permalink / raw)
  To: zimoun; +Cc: 33463-done

Hi Simon,

zimoun <zimon.toutoune@gmail.com> writes:
> This old bug [1] is about Hydra which is down now, IIRC.
>
> Does it make sense to keep it open?

I think it's okay to close it.  I'm doing so now.

     Thanks!
       Mark

-- 
Disinformation flourishes because many people care deeply about injustice
but very few check the facts.  Ask me about <https://stallmansupport.org>.




^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-09-16  8:18 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2021-09-16  8:15   ` Mark H Weaver

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).