From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 114212 invoked by alias); 28 Jun 2019 23:47:25 -0000 Mailing-List: contact elfutils-devel-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Post: List-Help: List-Subscribe: Sender: elfutils-devel-owner@sourceware.org Received: (qmail 114201 invoked by uid 89); 28 Jun 2019 23:47:25 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Checked: by ClamAV 0.100.3 on sourceware.org X-Virus-Found: No X-Spam-SWARE-Status: No, score=-6.0 required=5.0 tests=AWL,BAYES_00,KAM_ASCII_DIVIDERS,SPF_PASS autolearn=no version=3.3.1 spammy=gcov, OTHER, 1073741824, srv X-Spam-Status: No, score=-6.0 required=5.0 tests=AWL,BAYES_00,KAM_ASCII_DIVIDERS,SPF_PASS autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on sourceware.org X-Spam-Level: X-HELO: gnu.wildebeest.org Received: from wildebeest.demon.nl (HELO gnu.wildebeest.org) (212.238.236.112) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 28 Jun 2019 23:47:23 +0000 Received: from librem.wildebeest.org (deer0x15.wildebeest.org [172.31.17.151]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 20ABC30014BB for ; Sat, 29 Jun 2019 01:47:20 +0200 (CEST) Received: by librem.wildebeest.org (Postfix, from userid 1000) id A2D44C12F5; Sat, 29 Jun 2019 01:47:20 +0200 (CEST) Date: Fri, 28 Jun 2019 23:47:00 -0000 From: Mark Wielaard To: elfutils-devel@sourceware.org Subject: Re: Buildbot failure in Wildebeest Builder on whole buildset Message-ID: <20190628234720.GA4777@wildebeest.org> References: <20190628230202.6BD2E81A941@builder.wildebeest.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190628230202.6BD2E81A941@builder.wildebeest.org> User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Flag: NO X-IsSubscribed: yes X-SW-Source: 2019-q2/txt/msg00133.txt.bz2 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.