On Tue, 12 Dec 2023, Maciej W. Rozycki wrote: > Hi, > > This patch quasi-series makes it possible for individual test cases > identified as being slow to request more time via the GCC test harness by > providing a test execution timeout factor, applied to the tool execution > timeout set globally for all the test cases. This is to avoid excessive > testsuite run times where other test cases do hang as it would be the > case if the timeout set globally was to be increased. > > The test execution timeout is different from the tool execution timeout > where it is GCC execution that is being guarded against taking excessive > amount of time on the test host rather than the resulting test case > executable run on the target afterwards, as concerned here. GCC already > has a `dg-timeout-factor' setting for the tool execution timeout, but has > no means to increase the test execution timeout. The GCC side of these > changes adds a corresponding `dg-test-timeout-factor' setting.
Hmm. I think it would be more correct to emphasize that the existing dg-timeout-factor affects both the tool execution *and* the test execution, whereas your new dg-test-timeout-factor only affects the test execution. (And still measured on the host.) Usually the compilation time is close to 0, so is this based on an actual need more than an itchy "wart"? Or did I miss something? brgds, H-P
