From: Florian Weimer <fw@deneb.enyo.de>
To: Mark Wielaard <mjw@redhat.com>
Cc: Roland McGrath <roland@hack.frob.com>,
libc-alpha@sourceware.org, tuliom@quites.com.br
Subject: Re: [glibc-buildbot] Add 'glibc-s390x-linux': 'marist-fedora-s390x' to builder_map.
Date: Wed, 05 Oct 2016 21:34:00 -0000 [thread overview]
Message-ID: <87lgy232fe.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <1475696860.21750.67.camel@redhat.com> (Mark Wielaard's message of "Wed, 05 Oct 2016 21:47:40 +0200")
* 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.
prev parent reply other threads:[~2016-10-05 21:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 22:52 Mark Wielaard
2016-10-03 23:14 ` Carlos O'Donell
2016-10-03 23:31 ` Roland McGrath
2016-10-04 14:15 ` Mark Wielaard
2016-10-04 19:01 ` Roland McGrath
2016-10-05 19:47 ` Mark Wielaard
2016-10-05 20:13 ` Joseph Myers
2016-10-05 21:34 ` Florian Weimer [this message]
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=87lgy232fe.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=libc-alpha@sourceware.org \
--cc=mjw@redhat.com \
--cc=roland@hack.frob.com \
--cc=tuliom@quites.com.br \
/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).