diff options
| author | Hans-Peter Nilsson <hp@bitrange.com> | 2021-08-08 04:16:48 +0200 |
|---|---|---|
| committer | Hans-Peter Nilsson <hp@bitrange.com> | 2021-08-08 10:52:50 +0200 |
| commit | e9b639c4b532212ca92b2261f820768993770daa (patch) | |
| tree | 2d6527d4bb5191a2a7ba356e4847165f8e5f7505 /gcc/timevar.c | |
| parent | 7b51202c2a02c24e70b1924d468186130b2c09b7 (diff) | |
| download | gcc-e9b639c4b532212ca92b2261f820768993770daa.zip gcc-e9b639c4b532212ca92b2261f820768993770daa.tar.gz gcc-e9b639c4b532212ca92b2261f820768993770daa.tar.bz2 | |
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.
Diffstat (limited to 'gcc/timevar.c')
0 files changed, 0 insertions, 0 deletions