These tests have always been failing for my cris-elf
autotester running a simulator; they take about 20 minutes
each, compared to the timeout of 720 seconds, doubled
because they timed out in another simulator setup.
They are the *only* libstdc++ tests that timeout for my
setup so I thought this'd be best fixed in the testsuite
rather than a local timeout setting (in e.g. the baseboard
file). And, better make it an increase that counts. Or,
maybe they're actually needlessly excessive? FWIW, running
the whole libstdc++ testsuite for this target takes 2h40min.
Ok?
* testsuite/27_io/basic_istream/get/char/lwg3464.cc: Increase
timeout factor to 20.
* testsuite/27_io/basic_istream/get/wchar_t/lwg3464.cc: Likewise.
---
libstdc++-v3/testsuite/27_io/basic_istream/get/char/lwg3464.cc | 2 +-
.../testsuite/27_io/basic_istream/get/wchar_t/lwg3464.cc | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/libstdc++-v3/testsuite/27_io/basic_istream/get/char/lwg3464.cc
b/libstdc++-v3/testsuite/27_io/basic_istream/get/char/lwg3464.cc
index f426ff7dd867..69612375cba0 100644
--- a/libstdc++-v3/testsuite/27_io/basic_istream/get/char/lwg3464.cc
+++ b/libstdc++-v3/testsuite/27_io/basic_istream/get/char/lwg3464.cc
@@ -16,7 +16,7 @@
// <http://www.gnu.org/licenses/>.
// { dg-do run { target { ! lp64 } } }
-// { dg-timeout-factor 2 }
+// { dg-timeout-factor 20 }
#include <istream>
#include <streambuf>
diff --git a/libstdc++-v3/testsuite/27_io/basic_istream/get/wchar_t/lwg3464.cc
b/libstdc++-v3/testsuite/27_io/basic_istream/get/wchar_t/lwg3464.cc
index 4be6beb2310f..5f07c6d9880d 100644
--- a/libstdc++-v3/testsuite/27_io/basic_istream/get/wchar_t/lwg3464.cc
+++ b/libstdc++-v3/testsuite/27_io/basic_istream/get/wchar_t/lwg3464.cc
@@ -16,7 +16,7 @@
// <http://www.gnu.org/licenses/>.
// { dg-do run { target { ! lp64 } } }
-// { dg-timeout-factor 2 }
+// { dg-timeout-factor 20 }
#include <istream>
#include <streambuf>
--
2.30.2
