From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: bug#36754: SSH connections to hydra-slave{1, 2, 3} fail during builds (was: New linux-libre failed to build on armhf on Berlin) Date: Tue, 23 Jul 2019 13:33:09 -0400 Message-ID: <87ef2gr6z3.fsf@netris.org> References: <87o91n3ps0.fsf@netris.org> <87o91n3ps0.fsf@netris.org> <87zhl656xk.fsf@netris.org> <87pnm04s21.fsf@devup.no> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:54257) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hpyhn-0002oc-9L for bug-guix@gnu.org; Tue, 23 Jul 2019 13:36:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hpyhm-00070F-47 for bug-guix@gnu.org; Tue, 23 Jul 2019 13:36:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:54991) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hpyhm-00070B-0O for bug-guix@gnu.org; Tue, 23 Jul 2019 13:36:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hpyhl-0001Ga-RQ for bug-guix@gnu.org; Tue, 23 Jul 2019 13:36:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87pnm04s21.fsf@devup.no> 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: Marius Bakke Cc: 36754@debbugs.gnu.org retitle 36754 SSH connections to hydra-slave{1,2,3} fail during builds thanks Hi, I've added Ludovic to the CC list, since he recently added hydra-slave{1,2,3} to Berlin. Marius wrote: > I tried building 5.2.2 'interactively' on Berlin, and got an SSH error: >=20 > CC [M] net/openvswitch/vport-geneve.o > CC [M] net/openvswitch/vport-gre.o > LD [M] net/openvswitch/openvswitch.o > ;;; [2019/07/23 05:14:53.501502, 0] read_from_channel_port: [GSSH ERROR] = Error reading from the channel: # > Backtrace: > 16 (apply-smob/1 #) > In ice-9/boot-9.scm: > 705:2 15 (call-with-prompt _ _ #) > In ice-9/eval.scm: > 619:8 14 (_ #(#(#))) > In guix/ui.scm: > 1747:12 13 (run-guix-command _ . _) > In guix/scripts/offload.scm: > 781:22 12 (guix-offload . _) > In ice-9/boot-9.scm: > 829:9 11 (catch _ _ # =E2=80=A6) > 829:9 10 (catch _ _ # =E2=80=A6) > In guix/scripts/offload.scm: > 580:19 9 (process-request _ _ _ _ #:print-build-trace? _ # _ # _) > 531:6 8 (call-with-timeout _ _ _) > 361:2 7 (transfer-and-offload # =E2=80=A6) > In ice-9/boot-9.scm: > 829:9 6 (catch _ _ # =E2=80=A6) > In guix/scripts/offload.scm: > 385:6 5 (_) > In guix/store.scm: > 1203:15 4 (_ # _ _) > 692:11 3 (process-stderr # _) > In guix/serialization.scm: > 87:11 2 (read-int _) > 73:12 1 (get-bytevector-n* # =E2=80=A6) > In unknown file: > 0 (get-bytevector-n # =E2=80=A6) >=20 > ERROR: In procedure get-bytevector-n: > Throw to key `guile-ssh-error' with args `("read_from_channel_port" "Erro= r reading from the channel" # #f)'. > guix build: error: build of `/gnu/store/yfns7ga468vmv9jn72snk79b16p8mhfa-= linux-libre-5.2.2.drv' failed >=20 > real 637m24.906s > user 0m6.661s > sys 0m0.897s Thank you, this is helpful. > Unfortunately I failed to record which machine was used and don't know a > way to find out after the fact. I believe it was hydra-slave2, one of the three armhf machines that I host which were formerly part of hydra.gnu.org's build farm and were recently added to Berlin by Ludovic. I checked hydra-slave{1,2,3} for build log files corresponding to the derivation above, and found that all three of them have been attempted recently: hydra-slave2 attempted to build it on July 23 08:07 UTC. hydra-slave3 attempted to build it on July 22 16:40 UTC. hydra-slave1 attempted to build it on July 22 04:44 UTC. To be precise, each of those dates correspond to the end of the build attempt. All three build logs are truncated on the build machine as well, with no error message at the end. I now believe that these failures are related to the newly added armhf build slaves, and that they have nothing to do with the recent changes to our linux-libre packages. Well, except for the silence timeout that sometimes happens on slower machines while deblobbing linux-libre. That's a separate issue. Thanks, Mark