From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: bug#37246: Cuirass builds spuriously fail with truncated build logs Date: Sat, 31 Aug 2019 13:43:27 -0400 Message-ID: <875zmd9qn9.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:40991) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i47Qt-0006V8-Lr for bug-guix@gnu.org; Sat, 31 Aug 2019 13:45:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i47Qs-00027b-GS for bug-guix@gnu.org; Sat, 31 Aug 2019 13:45:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:47108) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1i47Qs-00027Q-Dm for bug-guix@gnu.org; Sat, 31 Aug 2019 13:45:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1i47Qs-0004wU-Af for bug-guix@gnu.org; Sat, 31 Aug 2019 13:45:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Received: from eggs.gnu.org ([2001:470:142:3::10]:40923) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i47Q2-0006Ql-T2 for bug-guix@gnu.org; Sat, 31 Aug 2019 13:44:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i47Q1-0001M3-RW for bug-guix@gnu.org; Sat, 31 Aug 2019 13:44:10 -0400 Received: from world.peace.net ([64.112.178.59]:35842) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1i47Q1-0001K9-OV for bug-guix@gnu.org; Sat, 31 Aug 2019 13:44:09 -0400 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: 37246@debbugs.gnu.org Cuirass builds sometimes spuriously fail with truncated build logs. Recent examples: https://ci.guix.gnu.org/build/1643344/details https://ci.guix.gnu.org/build/1632149/details Previously, we've noticed that this problem happens quite frequently with armhf builds offloaded to hydra-slave{1,2,3}, which are hosted far from Berlin. The examples above show that this problem also happens with build slaves that are local to Berlin. Mark