Hans-Peter Nilsson wrote:
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 (for the applicable tests). Notably, modulo bugs in
the test-suites.
The dg-timeout-factor tag is a GCC testsuite feature; the dg-patience
tag will be an upstream DejaGnu framework feature using shared
infrastructure also available to tests not using dg.exp. Improved
timeout handling will also eventually include per-target timeout
defaults and scale factors, to allow testing sites to adjust timeouts
for slow (or fast) targets.
Of course, it may be useful to separate different timeouts of
separable parts of a test - compilation and execution being the
topic at hand. But IMHO, YAGNI. Having said that, don't let
that stand in the way of a fun hack!
It will go on the TODO list either way; the only difference is the
priority it will have.
-- Jacob
