From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: 33410@debbugs.gnu.org
Subject: bug#33410: Offloaded builds can get stuck indefinitely due to network issues
Date: Sat, 17 Nov 2018 15:21:32 +0100 [thread overview]
Message-ID: <87efbjokcz.fsf@gnu.org> (raw)
In-Reply-To: <87a7m8xs42.fsf@netris.org> (Mark H. Weaver's message of "Fri, 16 Nov 2018 23:08:50 -0500")
Hello,
Mark H Weaver <mhw@netris.org> skribis:
> I just discovered that 4 out of 5 armhf build slots on Hydra have been
> stuck for 24 hours, apparently after the network connections to the
> build slaves were lost, possibly due to a temporary network outage.
>
> I've seen this kind of thing happen periodically since we switched to
> using guile-ssh for offloaded builds.
Which guix-daemon version is hydra running?
Commit a708de151c255712071e42e5c8284756b51768cd adds a safeguard to make
sure timeouts are honored, though there might be some cases where it
doesn’t quite work as expected (I suspect libssh handles EINTR
internally by looping, in which case our signal handling async doesn’t
get a chance to run.)
> On Hydra I can monitor the builds and investigate when a given build
> seems to be taking far too long, and I can kill those jobs to free up
> the build slots. There's no way to kill the builds from Hydra's web
> interface, but I can kill them manually by logging into Hydra.
>
> This might become a more serious problem on Berlin, as we add ARM build
> slaves that are not on the same local network as Berlin itself, until
> the web interface allows for this kind of monitoring and intervention.
The current situation on berlin is suboptimal: I run ‘guix processes’
when I suspect something is wrong, and that’s how I found about
<https://issues.guix.info/issue/33239>.
Thanks,
Ludo’.
prev parent reply other threads:[~2018-11-17 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-17 4:08 bug#33410: Offloaded builds can get stuck indefinitely due to network issues Mark H Weaver
2018-11-17 14:21 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87efbjokcz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33410@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.