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 <m...@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



Reply via email to