Re: [PATCH DejaGNU/GCC 0/1] Support per-test execution timeout factor

On Wed, 3 Jan 2024, Hans-Peter Nilsson wrote: > > > 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

Re: Generalizing DejaGnu timeout scaling (was: Re: [PATCH DejaGNU/GCC 0/1] Support per-test execution timeout factor)

On Wed, 3 Jan 2024, Jacob Bachmeyer wrote: > Comments before I start on an implementation? I'd suggest to await the conclusion of the debate: I *think* I've proved that dg-timeout-factor is already active as intended (all parts of a test), specifically when the compilation result is executed (f

Re: [PATCH DejaGNU/GCC 0/1] Support per-test execution timeout factor

On Wed, 3 Jan 2024, Maciej W. Rozycki wrote: > On Wed, 3 Jan 2024, Hans-Peter Nilsson wrote: > > > > 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 r

Generalizing DejaGnu timeout scaling (was: Re: [PATCH DejaGNU/GCC 0/1] Support per-test execution timeout factor)

Maciej W. Rozycki wrote: On Wed, 3 Jan 2024, Hans-Peter Nilsson wrote: 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 execu

Re: [PATCH DejaGNU/GCC 0/1] Support per-test execution timeout factor

"Maciej W. Rozycki" writes: > On Wed, 3 Jan 2024, Hans-Peter Nilsson wrote: > >> > 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

Re: [PATCH DejaGNU/GCC 0/1] Support per-test execution timeout factor

On Wed, 3 Jan 2024, Hans-Peter Nilsson wrote: > > 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 t

Re: [PATCH DejaGNU/GCC 0/1] Support per-test execution timeout factor

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 glob