From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 19780@debbugs.gnu.org
Subject: bug#19780: 13 failing tests
Date: Tue, 10 Feb 2015 15:59:01 +0100 [thread overview]
Message-ID: <idjvbj96cei.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <87sied7s9p.fsf@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?
next prev parent reply other threads:[~2015-02-10 15:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <idj4mhv15e4.fsf@bimsb-sys02.mdc-berlin.net>
2015-02-05 13:55 ` bug#19781: 13 failing tests Ricardo Wurmus
2015-02-07 15:45 ` bug#19781: Close Andreas Enge
2015-02-07 17:19 ` bug#19780: 13 failing tests Ludovic Courtès
2015-02-10 12:03 ` Ricardo Wurmus
2015-02-10 12:42 ` Ludovic Courtès
2015-02-10 14:15 ` Ricardo Wurmus
2015-02-10 14:30 ` Ludovic Courtès
2015-02-10 14:59 ` Ricardo Wurmus [this message]
2015-02-10 15:49 ` Ludovic Courtès
2015-02-10 16:45 ` Ricardo Wurmus
2015-02-10 17:08 ` Ludovic Courtès
2015-02-11 11:25 ` Ricardo Wurmus
2015-02-11 11:47 ` Ricardo Wurmus
2015-02-11 12:40 ` Ricardo Wurmus
2015-02-13 9:14 ` Ludovic Courtès
2015-02-13 10:33 ` Ricardo Wurmus
2015-02-13 13:20 ` Ludovic Courtès
2015-02-26 16:49 ` Ludovic Courtès
2015-02-28 21:58 ` Ricardo Wurmus
2015-03-02 15:57 ` Ricardo Wurmus
2015-03-03 8:04 ` Ludovic Courtès
2015-03-31 21:18 ` Ludovic Courtès
2015-02-13 13:23 ` Ludovic Courtès
2015-02-13 15:14 ` Ricardo Wurmus
2015-02-13 22:38 ` Ludovic Courtès
2015-10-13 9:59 ` bug#19780: “User has no home directory” (was: bug#19780: 13 failing tests) Ricardo Wurmus
2015-10-13 12:29 ` bug#19780: “User has no home directory” 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=idjvbj96cei.fsf@bimsb-sys02.mdc-berlin.net \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=19780@debbugs.gnu.org \
--cc=ludo@gnu.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).