From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org
Subject: Re: Buildbot failure in Wildebeest Builder on whole buildset
Date: Fri, 28 Jun 2019 23:47:00 -0000 [thread overview]
Message-ID: <20190628234720.GA4777@wildebeest.org> (raw)
In-Reply-To: <20190628230202.6BD2E81A941@builder.wildebeest.org>
On Fri, Jun 28, 2019 at 11:02:02PM +0000, buildbot@builder.wildebeest.org wrote:
> The Buildbot has detected a failed build on builder whole buildset while building elfutils.
> Full details are available at:
> https://builder.wildebeest.org/buildbot/#builders/1/builds/376
>
> Buildbot URL: https://builder.wildebeest.org/buildbot/
>
> Worker for this Build: centos-x86_64
The test-suite.log says:
FAIL: run-large-elf-file.sh
===========================
long_bit: 64
space_available: 38
mem_available: 7
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB) copied, 3.72662 s, 288 MB/s
addsections 2 testfile38 2147483648
add_sections 'testfile38': 2 (sec_size: 2147483648)
setshstrndx: 10
strip -o testfile38.strip -f testfile38.debug testfile38
elflint --gnu testfile38.strip
No errors
elflint --gnu -d testfile38.debug
No errors
unstrip testfile38.strip testfile38.debug
elfcmp testfile38.strip
addsections 2 testfile27 2147483648
add_sections 'testfile27': 2 (sec_size: 2147483648)
setshstrndx: 30
strip -o testfile27.strip -f testfile27.debug testfile27
/srv/buildbot/worker/elfutils-centos-x86_64/build/elfutils-0.176/_build/src/strip: while writing 'testfile27.debug.SjHGU1': out of memory
And the config.log has:
=====================================================================
elfutils: 0.176 (eu_version: 176)
=====================================================================
Prefix : /srv/buildbot/worker/elfutils-centos-x8
6_64/build/elfutils-0.176/_inst
Program prefix ("eu-" recommended) : eu-
Source code location : ..
Maintainer mode :
libebl modules subdirectory : elfutils
build arch : x86_64-unknown-linux-gnu
RECOMMENDED FEATURES (should all be yes)
gzip support : yes
bzip2 support : yes
lzma/xz support : yes
libstdc++ demangle support : yes
File textrel check : yes
Symbol versioning : yes
NOT RECOMMENDED FEATURES (should all be no)
Experimental thread safety : no
install elf.h : no
OTHER FEATURES
Deterministic archives by default : false
Native language support : yes
EXTRA TEST FEATURES (used with make check)
have bunzip2 installed (required) : yes
debug branch prediction : no
gprof support : no
gcov support : no
run all tests under valgrind : yes
gcc undefined behaviour sanitizer : no
use rpath in tests : no
test biarch : yes
So, this is running the test under valgrind.
In which case we might need even more free memory available.
The test did succeed earlier on the worker, not under valgrind.
next prev parent reply other threads:[~2019-06-28 23:47 UTC|newest]
Thread overview: 153+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 23:02 buildbot
2019-06-28 23:47 ` Mark Wielaard [this message]
2019-07-01 15:12 ` Mark Wielaard
-- strict thread matches above, loose matches on Subject: below --
2022-02-07 20:27 buildbot
2022-02-07 20:46 ` Mark Wielaard
2022-02-07 22:29 ` Mark Wielaard
2022-02-08 10:18 ` Mark Wielaard
2022-01-07 18:02 buildbot
2021-12-21 16:34 buildbot
2021-12-21 13:36 buildbot
2021-12-17 18:34 buildbot
2021-12-16 1:10 buildbot
2021-12-16 17:05 ` Mark Wielaard
2021-12-10 19:56 buildbot
2021-12-11 16:16 ` Mark Wielaard
2021-12-08 17:20 buildbot
2021-12-08 22:08 ` Mark Wielaard
2021-11-15 10:56 buildbot
2021-11-15 11:37 ` Mark Wielaard
2021-11-04 20:14 buildbot
2021-11-05 9:28 ` Mark Wielaard
2021-10-18 13:45 buildbot
2021-10-18 13:50 ` Mark Wielaard
2021-09-16 15:00 buildbot
2021-09-16 16:16 ` Mark Wielaard
2021-09-12 23:16 buildbot
2021-09-13 9:06 ` Mark Wielaard
2021-09-14 11:05 ` Mark Wielaard
2021-09-12 21:56 buildbot
2021-09-12 22:30 ` Mark Wielaard
2021-09-10 5:54 buildbot
2021-09-10 4:42 buildbot
2021-09-10 1:00 buildbot
2021-09-09 16:05 buildbot
2021-09-07 1:51 buildbot
2021-09-07 0:29 buildbot
2021-09-06 21:44 buildbot
2021-09-03 14:08 buildbot
2021-09-03 23:47 ` Mark Wielaard
2021-09-06 15:07 ` Mark Wielaard
2021-09-06 20:02 ` Mark Wielaard
2021-09-06 21:14 ` Mark Wielaard
2021-09-07 0:12 ` Mark Wielaard
2021-09-07 8:34 ` Dmitry V. Levin
2021-09-07 22:04 ` Mark Wielaard
2021-09-03 10:33 buildbot
2021-09-03 11:14 ` Mark Wielaard
2021-08-27 23:19 buildbot
2021-08-28 14:01 ` Mark Wielaard
2021-08-28 14:41 ` Frank Ch. Eigler
2021-08-27 21:20 buildbot
2021-08-28 12:29 ` Mark Wielaard
2021-08-11 23:16 buildbot
2021-08-23 20:48 ` Mark Wielaard
2021-08-04 15:13 buildbot
2021-08-05 14:19 ` Mark Wielaard
2021-07-22 17:21 buildbot
2021-07-22 14:24 buildbot
2021-07-22 14:36 ` Mark Wielaard
2021-07-19 16:33 buildbot
2021-07-08 9:53 buildbot
2021-07-08 9:56 ` Mark Wielaard
2021-06-15 21:29 buildbot
2021-06-15 21:40 ` Mark Wielaard
2021-06-15 21:53 ` Frank Ch. Eigler
2021-06-15 22:14 ` Mark Wielaard
2021-06-15 23:00 ` Frank Ch. Eigler
2021-06-16 9:35 ` Mark Wielaard
2021-06-12 23:39 buildbot
2021-06-12 23:53 ` Mark Wielaard
2021-04-15 12:53 buildbot
2021-04-13 16:54 buildbot
2021-04-14 12:13 ` Mark Wielaard
2021-04-13 14:29 buildbot
2021-04-14 12:06 ` Mark Wielaard
2021-03-31 11:29 buildbot
2021-03-31 11:37 ` Mark Wielaard
2021-03-07 19:11 buildbot
2021-03-06 14:45 buildbot
2021-03-06 15:46 ` Mark Wielaard
2021-03-02 12:45 buildbot
2021-03-02 11:53 buildbot
2021-03-02 4:28 buildbot
2021-03-01 19:56 buildbot
2021-03-01 22:13 ` Mark Wielaard
2021-02-17 22:22 buildbot
2021-02-12 18:45 buildbot
2021-02-12 16:40 buildbot
2021-02-09 2:26 buildbot
2021-02-09 9:05 ` Mark Wielaard
2021-02-12 15:58 ` Mark Wielaard
2021-02-12 19:09 ` Mark Wielaard
2020-12-16 23:54 buildbot
2020-12-16 23:58 ` Mark Wielaard
2020-12-12 17:11 buildbot
2020-12-12 18:47 ` Mark Wielaard
2020-11-28 4:15 buildbot
2020-11-28 13:41 ` Mark Wielaard
2020-11-28 15:12 ` Mark Wielaard
2020-11-29 1:18 ` Mark Wielaard
2020-11-23 17:50 buildbot
2020-11-23 17:58 ` Mark Wielaard
2020-11-19 13:26 buildbot
2020-11-19 13:55 ` Mark Wielaard
2020-11-17 15:09 buildbot
2020-11-17 17:10 ` Mark Wielaard
2020-10-31 2:12 buildbot
2020-10-31 10:22 ` Mark Wielaard
2020-10-30 15:41 buildbot
2020-10-30 1:51 buildbot
2020-10-30 8:45 ` Mark Wielaard
2020-10-08 16:45 buildbot
2020-10-08 17:38 ` Mark Wielaard
2020-06-19 23:20 buildbot
2020-06-19 23:47 ` Mark Wielaard
2020-06-11 16:00 buildbot
2020-06-11 16:15 ` Mark Wielaard
2020-03-26 16:53 buildbot
2020-03-25 23:48 buildbot
2020-03-26 9:15 ` Mark Wielaard
2020-03-23 13:38 buildbot
2020-03-23 14:08 ` Mark Wielaard
2020-03-23 23:06 ` Mark Wielaard
2020-03-04 12:09 buildbot
2020-03-04 12:45 ` Mark Wielaard
2020-02-26 21:42 buildbot
2020-02-26 21:59 ` Mark Wielaard
2020-02-10 22:34 buildbot
2020-02-21 12:10 ` Mark Wielaard
2020-02-10 19:11 buildbot
2020-01-20 21:05 buildbot
2020-01-20 19:44 buildbot
2020-01-17 0:08 buildbot
2019-12-03 9:49 buildbot
2019-12-03 10:23 ` Mark Wielaard
2019-11-23 2:25 buildbot
2019-11-23 1:38 buildbot
2019-10-26 2:47 buildbot
2019-10-26 12:08 ` Mark Wielaard
2019-09-07 14:54 buildbot
2019-09-07 19:53 ` Mark Wielaard
2019-08-29 13:59 buildbot
2019-08-29 14:23 ` Mark Wielaard
2019-08-29 15:52 ` Mark Wielaard
2019-08-28 22:08 buildbot
2019-08-28 22:13 ` Mark Wielaard
2019-08-15 8:28 buildbot
2018-11-13 16:42 buildbot
2018-11-13 17:29 ` Mark Wielaard
2018-11-13 20:46 ` Mark Wielaard
2018-11-10 12:32 buildbot
2018-11-10 12:36 ` Mark Wielaard
2018-11-06 14:15 buildbot
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=20190628234720.GA4777@wildebeest.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.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.
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).