From: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
To: Szabolcs Nagy via Libc-alpha <libc-alpha@sourceware.org>
Cc: Szabolcs Nagy <szabolcs.nagy@arm.com>
Subject: Re: glibc 2.34
Date: Mon, 02 Aug 2021 13:52:37 +0200 [thread overview]
Message-ID: <87mtq0qd16.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20210802111645.GG14854@arm.com> (Szabolcs Nagy via Libc-alpha's message of "Mon, 2 Aug 2021 12:16:46 +0100")
* Szabolcs Nagy via Libc-alpha:
> The 08/02/2021 10:44, Paul Zimmermann wrote:
>> I just compiled GNU libc 2.34 on my workstation (Intel Core i5 under
>> Debian GNU/Linux 11 bullseye with gcc 10.2.1) and got 3 errors with
>> make check:
>>
>> Summary of test results:
>> 3 FAIL
>> 4439 PASS
>> 20 UNSUPPORTED
>> 16 XFAIL
>> 2 XPASS
>>
>> FAIL: io/tst-closefrom
>> FAIL: misc/tst-close_range
>> FAIL: posix/tst-spawn5
>>
>> $ cat io/tst-closefrom.out
>> tst-closefrom.c:38: numeric comparison failure
>> left: 95 (0x5f); from: xopen ("/dev/null", O_RDONLY, 0600)
>> right: 93 (0x5d); from: lowfd + i
>
> i see similar failure when the shell where i run
> the tests has inherited fds open (e.g. in this
> case fd 93 and 94)
Right, we saw that internally as well. I think we need a support/
utility that returns the maximum open file descriptor, plus 1, and
raises RLIMIT_NOFILE if necessary.
Thanks,
Florian
next prev parent reply other threads:[~2021-08-02 11:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 8:44 glibc 2.34 Paul Zimmermann
2021-08-02 11:16 ` Szabolcs Nagy via Libc-alpha
2021-08-02 11:36 ` Paul Zimmermann
2021-08-02 11:52 ` Florian Weimer via Libc-alpha [this message]
2021-08-04 13:41 ` Adhemerval Zanella via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mtq0qd16.fsf@oldenburg.str.redhat.com \
--to=libc-alpha@sourceware.org \
--cc=fweimer@redhat.com \
--cc=szabolcs.nagy@arm.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).