From: "Ludovic Courtès" <ludo@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: 34157@debbugs.gnu.org
Subject: bug#34157: Hydra: mozjs-60 builds on x86_64 and i686 seemingly get stuck
Date: Tue, 22 Jan 2019 14:24:51 +0100 [thread overview]
Message-ID: <878szcome4.fsf@gnu.org> (raw)
In-Reply-To: <87sgxlv1td.fsf@netris.org> (Mark H. Weaver's message of "Mon, 21 Jan 2019 21:54:43 -0500")
Hi Mark,
Mark H Weaver <mhw@netris.org> skribis:
> Those two builds are still occupying build slots. As I write this,
> they've been running for over 30 hours.
>
> I was curious whether the transfers were actually happening, even if
> slowly, so I looked at 'netstat' output:
>
> root@20121227-hydra:~# netstat --inet --program | grep net.in.tum
> tcp 0 0 20121227-hydra.gn:58007 hydra.net.in.tum.de:ssh ESTABLISHED 18774/guile
> tcp 0 0 20121227-hydra.gn:42586 hydra.net.in.tum.de:ssh ESTABLISHED 10042/guile
> tcp 0 0 20121227-hydra.gn:56413 hydra.net.in.tum.de:ssh ESTABLISHED 16236/guile
>
> There are currently three builds allocated to hydra.gnunet.org
> (a.k.a. hydra.net.in.tum), so it appears that all three ssh connections
> are still active. However, even after repeating this command many
> times, I've never seen a non-zero "Send-Q" value. This suggests that no
> data is actually being sent, but that it's stuck waiting for something.
Weird.
> I'll leave these builds alone for now, in case Ludovic wants to
> investigate further.
I think you can terminate them as I’d rather not commit to investigate
further now.
I believe hydra.gnu.org is still running a rather old
guix-daemon/offload, right? We should upgrade to the latest and
greatest to make sure we’re after a bug that’s still present.
Thanks,
Ludo’.
prev parent reply other threads:[~2019-01-22 19:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 15:31 bug#34157: Hydra: mozjs-60 builds on x86_64 and i686 seemingly get stuck Mark H Weaver
2019-01-21 15:39 ` Efraim Flashner
2019-01-22 2:54 ` Mark H Weaver
2019-01-22 13:24 ` Ludovic Courtès [this message]
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=878szcome4.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=34157@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 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).