From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 39035 invoked by alias); 5 Oct 2016 21:34:55 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 39025 invoked by uid 89); 5 Oct 2016 21:34:55 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.5 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=sk:tst-get, sk:tstget, HCc:D*br, HCc:D*com.br X-HELO: albireo.enyo.de From: Florian Weimer To: Mark Wielaard Cc: Roland McGrath , libc-alpha@sourceware.org, tuliom@quites.com.br Subject: Re: [glibc-buildbot] Add 'glibc-s390x-linux': 'marist-fedora-s390x' to builder_map. References: <1475535138-12482-1-git-send-email-mjw@redhat.com> <20161003233115.6C2C72C3B64@topped-with-meat.com> <1475590520.21750.29.camel@redhat.com> <20161004190107.4CDDF2C3B9D@topped-with-meat.com> <1475696860.21750.67.camel@redhat.com> Date: Wed, 05 Oct 2016 21:34:00 -0000 In-Reply-To: <1475696860.21750.67.camel@redhat.com> (Mark Wielaard's message of "Wed, 05 Oct 2016 21:47:40 +0200") Message-ID: <87lgy232fe.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2016-10/txt/msg00112.txt.bz2 * Mark Wielaard: > Where the FAILS are: > > FAIL: malloc/tst-malloc-thread-fail > FAIL: malloc/tst-mallocfork2 > FAIL: timezone/tst-tzset Do we dump the .out files somewhere, like we do for Fedora? Anyway, the three above are likely due to resource constraints, either RLIMIT_DATA/RLIMIT_AS, or RLIMIT_NPROC. The latter could come from a systemd task limit which is incorrectly enforced due to a kernel bug: The kernel says the thread is gone while it still counts against the limit, and those tests will spawn new threads prematurely, eventually exceeding RLIMIT_NPROC. timezone/tst-tzset points towards an RLIMIT_DATA/RLIMIT_AS limit, though. > FAIL: posix/tst-getaddrinfo4 This could be due to lack of network access. We could add a configure option like --disable-network-tests for that. > Can/should I ignore those (how?) or are these suspicious? The first three are somewhat suspicious, yes.