From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: bug#19780: 13 failing tests Date: Tue, 10 Feb 2015 15:59:01 +0100 Message-ID: References: <874mqxprk6.fsf@gnu.org> <87vbja7xat.fsf@gnu.org> <87sied7s9p.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42099) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YLCIN-0005A3-1K for bug-guix@gnu.org; Tue, 10 Feb 2015 10:00:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YLCIH-00072z-Fp for bug-guix@gnu.org; Tue, 10 Feb 2015 10:00:10 -0500 Received: from debbugs.gnu.org ([140.186.70.43]:48244) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YLCIH-00072k-Dj for bug-guix@gnu.org; Tue, 10 Feb 2015 10:00:05 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1YLCIH-0004V2-2Q for bug-guix@gnu.org; Tue, 10 Feb 2015 10:00:05 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87sied7s9p.fsf@gnu.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-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 19780@debbugs.gnu.org Ludovic Courtès writes: >> [rwurmus@guix-builder:/localhome/rwurmus-tmp/guix] (720) $ ./test-env guix build guile-bootstrap > > [...] > >> @ build-started /localhome/rwurmus-tmp/guix/test-tmp/store/m1cbz6gmyv2f5551j7zpm99d7mgy2zp9-guile-bootstrap-2.0.drv - x86_64-linux /localhome/rwurmus-tmp/guix/test-tmp/var/log/guix/drvs/m1//cbz6gmyv2f5551j7zpm99d7mgy2zp9-guile-bootstrap-2.0.drv.bz2 >> builder for `/localhome/rwurmus-tmp/guix/test-tmp/store/m1cbz6gmyv2f5551j7zpm99d7mgy2zp9-guile-bootstrap-2.0.drv' failed due to signal 11 (Segmentation fault) > > Could you “rm -rf /localhome/rwurmus-tmp/guix/test-tmp” and try again? Same after rm-rf'ing. > If that fails again, could you run ‘ulimit -c unlimited’ before running > the command, add see if we get a core dump from which to extract that > Bash backtrace? Oddly, I cannot seem to get a core dump, even after setting ulimit -c unlimited. Is there a way to run the failing builder manually?