From e9b639c4b532212ca92b2261f820768993770daa Mon Sep 17 00:00:00 2001 From: Hans-Peter Nilsson Date: Sun, 8 Aug 2021 04:16:48 +0200 Subject: [PATCH] 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. --- 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 #include