public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Adhemerval Zanella <azanella@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] stdlib: Tune down fork arc4random tests Date: Mon, 12 Jun 2023 17:58:29 +0000 (GMT) [thread overview] Message-ID: <20230612175829.1219D3858D20@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=e6ce346d0791410a2e6ec9df1bc35e6acd4bca18 commit e6ce346d0791410a2e6ec9df1bc35e6acd4bca18 Author: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org> Date: Thu Jun 1 12:59:19 2023 -0300 stdlib: Tune down fork arc4random tests There is no fork detection on current arc4random implementation, so use lower subprocess on fork tests. The tests now run on 0.1s instead of 8s on a Ryzen9 5900X. Checked on x86_64-linux-gnu. Reviewed-by: Carlos O'Donell <carlos@redhat.com> Diff: --- stdlib/tst-arc4random-fork.c | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/stdlib/tst-arc4random-fork.c b/stdlib/tst-arc4random-fork.c index a69ec3968f..65d5893f5e 100644 --- a/stdlib/tst-arc4random-fork.c +++ b/stdlib/tst-arc4random-fork.c @@ -30,14 +30,10 @@ #include <unistd.h> /* Perform multiple runs. The subsequent runs start with an - already-initialized random number generator. (The number 1500 was - seen to reproduce failures reliable in case of a race condition in - the fork detection code.) */ -enum { runs = 1500 }; - -/* One hundred processes in total. This should be high enough to - expose any issues, but low enough not to tax the overall system too - much. */ + already-initialized random number generator. */ +enum { runs = 10 }; + +/* Total number of spawned processes on each run. */ enum { subprocesses = 49 }; /* The total number of processes. */
reply other threads:[~2023-06-12 17:58 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230612175829.1219D3858D20@sourceware.org \ --to=azanella@sourceware.org \ --cc=glibc-cvs@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: linkBe 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).