On 28/03/2025 16:06:52+0800, David Gow wrote:
I'll get around to extending this to allow the "base timeout" to be configurable as a command-line option, too, if this seems like a good way to go.
- Mark rtc_time64_to_tm_test_date_range_1000 slow,
- Mark rtc_time64_to_tm_test_date_range_160000 very slow.
Hmm... these are definitely fast enough on my "modern" machine that they probably only warrant "slow", not "very slow". But given they're definitely causing problems on older machines, I'm happy to go with marking the large ones very slow. (I've been waiting for them for about 45 minutes so far on my 486.)
Note that as discussed elsewhere, I'm open to simply remove rtc_time64_to_tm_test_date_range_160000. It was a nice proof that he change was working at the time but I don't think it is necessary to check this range.