From: Hans-Peter Nilsson <hp@axis.com>
To: <gcc-patches@gcc.gnu.org>, <libstdc++@gcc.gnu.org>
Subject: [PATCH] libstdc++-v3: Set 26_numerics/random/n.b.d./op./values.cc timeout-factor to 3
Date: Fri, 20 May 2022 04:19:33 +0200 [thread overview]
Message-ID: <20220520021933.7CE782042B@pchp3.se.axis.com> (raw)
Also, how about shortening those test-suite file-paths?
They're path sort-of overlong for any git (and ChangeLog)
commit-line limit. 1/2 :-)
Ok to commit (without renaming)?
--- 8< ---
I happened to run my cris-elf regression-tester and some
large job in parallel when this test was running. According
to "time" it takes 4:39.07 for the GNU cris-elf simulator on
this yesteryear machine. The default timeout is 360
seconds. Let's "up" the time by a factor 3.
libstdc++-v3:
* testsuite/26_numerics/random/negative_binomial_distribution/operators/values.cc:
Set dg-timeout-factor to 3.
---
.../random/negative_binomial_distribution/operators/values.cc | 1 +
1 file changed, 1 insertion(+)
diff --git a/libstdc++-v3/testsuite/26_numerics/random/negative_binomial_distribution/operators/values.cc b/libstdc++-v3/testsuite/26_numerics/random/negative_binomial_distribution/operators/values.cc
index dda6f43b2540..89a2b3dc4b76 100644
--- a/libstdc++-v3/testsuite/26_numerics/random/negative_binomial_distribution/operators/values.cc
+++ b/libstdc++-v3/testsuite/26_numerics/random/negative_binomial_distribution/operators/values.cc
@@ -1,4 +1,5 @@
// { dg-do run { target c++11 } }
+// { dg-timeout-factor 3 }
// { dg-require-cstdint "" }
// { dg-require-cmath "" }
//
--
2.30.2
next reply other threads:[~2022-05-20 2:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 2:19 Hans-Peter Nilsson [this message]
2022-05-20 9:03 ` Jonathan Wakely
2022-05-20 9:22 ` Jonathan Wakely
2022-05-20 14:30 ` Hans-Peter Nilsson
2022-05-20 15:06 ` Jonathan Wakely
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=20220520021933.7CE782042B@pchp3.se.axis.com \
--to=hp@axis.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.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).