From mboxrd@z Thu Jan 1 00:00:00 1970 From: Efraim Flashner Subject: bug#34157: Hydra: mozjs-60 builds on x86_64 and i686 seemingly get stuck Date: Mon, 21 Jan 2019 17:39:47 +0200 Message-ID: <20190121153947.GD11658@macbook41> References: <87zhruuiv6.fsf@netris.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="AsxXAMtlQ5JHofzM" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:48441) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1glbgB-0007Kd-Q5 for bug-guix@gnu.org; Mon, 21 Jan 2019 10:40:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1glbgA-0001Yo-Ue for bug-guix@gnu.org; Mon, 21 Jan 2019 10:40:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:41064) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1glbgA-0001YW-QC for bug-guix@gnu.org; Mon, 21 Jan 2019 10:40:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1glbgA-0000UI-Ix for bug-guix@gnu.org; Mon, 21 Jan 2019 10:40:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <87zhruuiv6.fsf@netris.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Mark H Weaver Cc: 34157@debbugs.gnu.org --AsxXAMtlQ5JHofzM Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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: >=20 > https://hydra.gnu.org/build/3342528 > https://hydra.gnu.org/build/3343511 >=20 > In both cases, the build logs are empty, and the hydra log ends with: >=20 > sending 1 store item to 'hydra.gnunet.org'... > exporting path `/gnu/store/j2sz7dg35vkcz38sim71jll2ix1nk554-mozjs-60.2.= 3-2-checkout' >=20 > 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. >=20 > What do you think? >=20 > Mark >=20 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? --=20 Efraim Flashner =D7=90=D7=A4=D7=A8=D7=99=D7=9D = =D7=A4=D7=9C=D7=A9=D7=A0=D7=A8 GPG key =3D A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted --AsxXAMtlQ5JHofzM Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEoov0DD5VE3JmLRT3Qarn3Mo9g1EFAlxF578ACgkQQarn3Mo9 g1Fjyg/+KLxi3DQijzrjUc+eZRmbS/Sy5V9Y6Mh6li8/6xKrdsYP6WwSoQIPiuo3 Sbd+1wW98Naux/REQKM+kjlEEI2oBma5gv45A30TpicqRfaMIL+RAXDgTbdJtw5e 8i+hhlk7w5njn/4xtVjW+bOgEDm3Zj3nJEWBFtP9wSeAiF+UzjwAZ2pIXMZKmRVT Kr3z+Az7XaCcuTWkOEGe+2T4lcMe1hOF6EpYoIx28uq/2VHFMg6/zo19F7XSgy4u 2BspFAB+u96Vv10gWipzJ6+DBydstmjqZFcmNarBq5YBwLh/EKX+S2u88wB6Iiko jYZfpkP03sO5Yv4qlrBh5umvez9+o4vrDkO8OZVfS3PA2ukP3PMlrQkGiSz98pwN hMYyJdCTFTp/GECpVfMfUMcizj57YdusXtYU2W/QY4Z/4QinGbgzhoaHFGsi6+hk rCRbjEoAoX8I5l7QnrMq/nJEonQ30e/7YX01/We0St7BlTokHSsbkWwgcE+YBjBD Hbe622B+at1ryLVeDR00QNGlqcLEIlrdoAMLqoYoeUbqniYaihZpXselsDdjk3mo umr5v2y7Hqt9mxT5PuBh58S6vwRegLirvVG+58fLaggxSKRrR7/hcS+A7B3blQGc yTqcw6+Vlo56EUhf5zLUBdHSYnszy1QteL1PCRXUCKilxmO++eE= =MEwG -----END PGP SIGNATURE----- --AsxXAMtlQ5JHofzM--