From: Efraim Flashner <efraim@flashner.co.il>
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: Mon, 21 Jan 2019 17:39:47 +0200 [thread overview]
Message-ID: <20190121153947.GD11658@macbook41> (raw)
In-Reply-To: <87zhruuiv6.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
On Mon, Jan 21, 2019 at 10:31:46AM -0500, Mark H Weaver wrote:
> Yesterday on Hydra, I found both Intel mozjs-60 builds seemingly stuck
> while exporting the source checkout to hydra.gnunet.org. One had been
> going for ~22.5 hours, and the other for ~12 hours. I forcefully killed
> them and restarted them. Now I see the same thing has happened on the
> second attempt. Both builds have been seemingly stuck like this for
> about 19 hours:
>
> https://hydra.gnu.org/build/3342528
> https://hydra.gnu.org/build/3343511
>
> In both cases, the build logs are empty, and the hydra log ends with:
>
> sending 1 store item to 'hydra.gnunet.org'...
> exporting path `/gnu/store/j2sz7dg35vkcz38sim71jll2ix1nk554-mozjs-60.2.3-2-checkout'
>
> Of course, it's possible that they're not really stuck, but that they're
> merely taking a ridiculously long time to send the source checkout to
> the build slave. My personal checkout of the mozilla-esr60 branch,
> without the .hg directory, is about 2.1 gigabytes.
>
> What do you think?
>
> Mark
>
12 hours is far too long for it to tie up a build slave, sending code or
not. Being silent that long doesn't trigger the auto-kill?
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-01-21 15:40 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 [this message]
2019-01-22 2:54 ` Mark H Weaver
2019-01-22 13:24 ` Ludovic Courtès
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=20190121153947.GD11658@macbook41 \
--to=efraim@flashner.co.il \
--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).