On 26/11/20 16:25 +0000, Jonathan Wakely wrote:
>These tests are very, very slow to compile. If the testsuite is run with
>a low tool_timeout value they are likely to fail. By adding a
>multiplication factor to those tests, it's still possible to use a low
>timeout without spurious failures.
>
>libstdc++-v3/ChangeLog:
>
>	* testsuite/28_regex/algorithms/regex_match/basic/string_range_01_03.cc:
>	Add dg-timeout-factor directive.
>	* testsuite/28_regex/algorithms/regex_match/cstring_bracket_01.cc:
>	Likewise.
>	* testsuite/28_regex/algorithms/regex_match/ecma/char/backref.cc:
>	Likewise.
>	* testsuite/28_regex/algorithms/regex_match/ecma/wchar_t/63199.cc:
>	Likewise.
>	* testsuite/28_regex/algorithms/regex_match/ecma/wchar_t/anymatcher.cc:
>	Likewise.
>	* testsuite/28_regex/algorithms/regex_match/ecma/wchar_t/cjk_match.cc:
>	Likewise.
>	* testsuite/28_regex/algorithms/regex_match/ecma/wchar_t/hex.cc:
>	Likewise.
>	* testsuite/28_regex/algorithms/regex_match/extended/wstring_locale.cc:
>	Likewise.
>	* testsuite/28_regex/algorithms/regex_search/61720.cc: Likewise.
>	* testsuite/28_regex/algorithms/regex_search/ecma/assertion.cc:
>	Likewise.
>	* testsuite/28_regex/algorithms/regex_search/ecma/string_01.cc:
>	Likewise.
>	* testsuite/28_regex/basic_regex/ctors/deduction.cc: Likewise.
>

I've been experimenting with much shorter tool_timeout values for the
testsuite. We already knew that the PSTL and <regex> tests are slow,
and indeed they are more prone to FAILing if the default timeout is
too short.

This adds dg-timeout-factor to lots more tests, so that it's practical
to use "set tool_timeout 120" or even "set tool_timeout 60" without
too many problems.

Tested powerpc64le-linux, committed to trunk.