From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Subject: Re: glibc-2.36 failure
Date: Mon, 22 Aug 2022 13:55:24 -0300 [thread overview]
Message-ID: <ba98798e-0738-4309-6553-4f105e37deea@linaro.org> (raw)
In-Reply-To: <mwpmgspqxl.fsf@tomate.loria.fr>
On 22/08/22 06:29, Paul Zimmermann via Libc-alpha wrote:
> Hi,
>
> is the following failure known for glibc 2.36 make check?
>
> Summary of test results:
> 1 FAIL
> 5083 PASS
> 78 UNSUPPORTED
> 18 XFAIL
> 4 XPASS
>
> FAIL: stdlib/tst-arc4random-thread
>
> zimmerma@biscotte:/localdisk/zimmerma/glibc-2.36/build$ cat stdlib/tst-arc4random-thread.out
> info: outer_threads=8 inner_threads=4
> info: arc4random: minimum of 655360 blob results expected
> info: arc4random: 662011 blob results observed
> info: arc4random_buf: minimum of 655360 blob results expected
> info: arc4random_buf: 655360 blob results observed
> info: arc4random_uniform: minimum of 655360 blob results expected
> Timed out: killed the child process
> Termination time: 2022-08-22T08:57:46.154936205
> Last write to standard output: 2022-08-22T08:57:32.198256849
>
> I used ../configure --prefix=/usr, on a AMD EPYC 7282 16-Core Processor,
> with gcc version 12.1.0 (Debian 12.1.0-8).
I have seen the test timeout on some environments, I think we will need to
tune it down similar to what we have done for tst-arc4random-fork.
next prev parent reply other threads:[~2022-08-22 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 9:29 Paul Zimmermann
2022-08-22 16:55 ` Adhemerval Zanella Netto [this message]
2022-08-22 17:30 ` Florian Weimer
2022-08-23 8:32 ` Paul Zimmermann
2022-08-23 8:48 ` Florian Weimer
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=ba98798e-0738-4309-6553-4f105e37deea@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=libc-alpha@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).