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. As the two changes are independent from each other, they can be applied in any order with the feature becoming active once both have been placed in a given system. I chose to submit them together so as to give an opportunity to both DejaGNU and GCC developers to chime in. The DejaGNU side of this patch quasi-series relies on that patch series: <https://lists.gnu.org/archive/html/dejagnu/2023-12/msg00003.html> to be applied first, however I chose to post the two parts separately so as not to clutter the GCC mailing list with changes solely for DejaGNU. This has been verified with the GCC testsuite in a couple of environments using the Unix protocol, both locally and remotely, the GDB stub protocol, and the sim protocol, making sure that timeout settings are respected. I found no obvious way to verify the remaining parts, but the changes follow the same pattern, so they're expected to behave consistently. Let me know if you have any questions, comments or concerns. Otherwise please apply/approve respectively the DejaGNU/GCC side. Maciej