On Sun, 30 Jan 2022, 01:37 Hans-Peter Nilsson via Libstdc++, < libstd...@gcc.gnu.org> wrote:
> 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? They are testing behaviour when a counter overflows, so they have to read that many bytes. Making them do less work would not test that condition. But there is nothing target-specific in that code, so it should be fine to disable them for simulators. They're already disabled for LP64 because overflowing the 64-bit counter would take forever. I think that would be better than letting them potentially run for 40 minutes even on real hardware.
