public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r12-2799] libstdc++: Tweak timeout for testsuite/std/ranges/iota/max_size_type.cc Date: Sun, 8 Aug 2021 08:53:23 +0000 (GMT) [thread overview] Message-ID: <20210808085323.D90763857C5E@sourceware.org> (raw) https://gcc.gnu.org/g:e9b639c4b532212ca92b2261f820768993770daa commit r12-2799-ge9b639c4b532212ca92b2261f820768993770daa Author: Hans-Peter Nilsson <hp@bitrange.com> Date: Sun Aug 8 04:16:48 2021 +0200 libstdc++: Tweak timeout for testsuite/std/ranges/iota/max_size_type.cc A simulator can easily spend more than 10 minutes running this test-case, and the default timeout is at 5 minutes. Better allow even slower machines; use 4 as the factor. Regarding relative runtime numbers (very local; mmixware simulator for mmix-knuth-mmixware): test01 and test05 finish momentarily; test02 at about 2 minutes, and test03 about 2m30, but test04 itself runs for more than 6 minues and so times out. Not sure if it's better to split up this test, as the excessive runtime may be unintended, but this seemed simplest. libstdc++-v3: * testsuite/std/ranges/iota/max_size_type.cc: Set dg-timeout-factor to 4. Diff: --- libstdc++-v3/testsuite/std/ranges/iota/max_size_type.cc | 1 + 1 file changed, 1 insertion(+) diff --git a/libstdc++-v3/testsuite/std/ranges/iota/max_size_type.cc b/libstdc++-v3/testsuite/std/ranges/iota/max_size_type.cc index 983bdfbdaa6..a52e8e6231a 100644 --- a/libstdc++-v3/testsuite/std/ranges/iota/max_size_type.cc +++ b/libstdc++-v3/testsuite/std/ranges/iota/max_size_type.cc @@ -17,6 +17,7 @@ // { dg-options "-std=gnu++2a" } // { dg-do run { target c++2a } } +// { dg-timeout-factor 4 } #include <limits> #include <ranges>
reply other threads:[~2021-08-08 8:53 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=20210808085323.D90763857C5E@sourceware.org \ --to=hp@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@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: 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).