public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: elfutils-devel@sourceware.org
Subject: Re: ☠ Buildbot (GNU Toolchain): elfutils - failed test (failure) (master)
Date: Sat, 28 May 2022 11:04:07 +0200	[thread overview]
Message-ID: <YpHlh2jd643L2D4c@wildebeest.org> (raw)
In-Reply-To: <20220528023419.GA30283@redhat.com>

On Fri, May 27, 2022 at 10:34:19PM -0400, Frank Ch. Eigler wrote:
> Hi -
> 
> n-metrics.sh: line 198: 27160 Aborted                 (core dumped) env LD_LIBRARY_PATH=$ldpath ${abs_builddir}/../debuginfod/debuginfod $VERBOSE -d ${DB} -F -U -t0 -g0 -p $PORT1 L D F > vlog$PORT1 2>&1
> > [...]
> > Process 27160 (debuginfod) of user 994 killed by SIGABRT - ignoring (low free space)
> > Lets see what happens on a rebuild.
> 
> Did the machine run out of memory / storage?

Maybe, hard to tell from the logs. At the moment it looks like:

$ df -h
Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        3.7G     0  3.7G   0% /dev
tmpfs           3.7G     0  3.7G   0% /dev/shm
tmpfs           3.7G   17M  3.7G   1% /run
tmpfs           3.7G     0  3.7G   0% /sys/fs/cgroup
/dev/vda2        12G   11G  881M  93% /
/dev/vdb1        40G  8.3G   32G  21% /srv
tmpfs           748M     0  748M   0% /run/user/994
tmpfs           748M     0  748M   0% /run/user/1000
$ free -h
              total        used        free      shared  buff/cache   available
Mem:           7.3G        418M        2.4G         16M        4.5G        6.6G
Swap:          511M          0B        511M

So maybe / was slightly full. The buildbot itself runs under /srv/
I freed 2.5G from / and uninstalled abrt so it doesn't intercept
generating the core files.

Cheers,

Mark


  reply	other threads:[~2022-05-28  9:04 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27 16:02 builder
2022-05-27 22:30 ` Mark Wielaard
2022-05-28  2:34   ` Frank Ch. Eigler
2022-05-28  9:04     ` Mark Wielaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-14  2:51 builder
2022-12-21 18:22 builder
2022-12-19 23:56 builder
2022-12-12 14:31 builder
2022-11-28 13:30 builder
2022-11-04 22:29 builder
2022-11-03 15:27 builder
2022-11-02 13:39 builder
2022-11-02 14:19 ` Mark Wielaard
2022-11-02  1:15 builder
2022-11-02 12:06 ` Mark Wielaard
2022-11-01 21:28 builder
2022-10-31 13:51 builder
2022-10-27 19:25 builder
2022-10-17 14:59 builder
2022-10-17  9:08 builder
2022-10-17 10:26 ` Mark Wielaard
2022-10-17 11:02   ` Frank Ch. Eigler
2022-10-17 14:09     ` Frank Ch. Eigler
2022-10-16 21:02 builder
2022-10-16 15:47 builder
2022-10-16 16:26 ` Mark Wielaard
2022-10-13 16:51 builder
2022-09-14 19:36 builder
2022-07-31 23:54 builder
2022-08-01  0:09 ` Mark Wielaard
2022-08-01  9:13   ` Mark Wielaard
2022-05-28  9:15 builder
2022-05-28  9:35 ` Mark Wielaard
2022-05-28  9:43   ` Mark Wielaard
2022-06-02 15:44     ` Mark Wielaard
2022-05-14 15:34 builder
2022-05-14 16:40 ` Mark Wielaard
2022-05-14 14:42 builder
2022-05-04 15:34 builder
2022-05-04 17:44 ` Mark Wielaard
2022-04-23 13:19 builder
2022-04-23  1:19 builder
2022-04-23  1:31 ` Mark Wielaard
2022-04-19  9:05 builder
2022-04-19  9:28 ` Mark Wielaard

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YpHlh2jd643L2D4c@wildebeest.org \
    --to=mark@klomp.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=fche@redhat.com \
    /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.
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).