Maciej W. Rozycki wrote:
Add support for the `test_timeout_factor' global variable letting a test
case scale the wait timeout used for code execution. This is useful for
particularly slow test cases for which increasing the wait timeout
globally would be excessive.
* baseboards/qemu.
.
Any questions, comments, or concerns? Otherwise please apply.
Patches 1, 2, and 3 applied as offered on branch mwr-patch-20231212.
Patch 4 has been revised and applied on the branch because the command
to be executed is free-form text while the timeout is a simple number;
the revised format
On 12/12/23 07:04, Maciej W. Rozycki wrote:
Add support for the `dg-test-timeout-factor' keyword letting a test
case scale the wait timeout used for code execution, analogously to
`dg-timeout-factor' used for code compilation. This is useful for
particularly slow test cases for which increasi
On 12/12/23 07:04, Maciej W. Rozycki wrote:
Add support for the `test_timeout_factor' global variable letting a test
case scale the wait timeout used for code execution. This is useful for
particularly slow test cases for which increasing the wait timeout
globally would be excessive.
Add support for the `dg-test-timeout-factor' keyword letting a test
case scale the wait timeout used for code execution, analogously to
`dg-timeout-factor' used for code compilation. This is useful for
particularly slow test cases for which increasing the wait timeout
globally would be excessive.
Add support for the `test_timeout_factor' global variable letting a test
case scale the wait timeout used for code execution. This is useful for
particularly slow test cases for which increasing the wait timeout
globally would be excessive.
* baseboards/qemu.exp (qemu_load): Handle `te
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
t
Report both the full command and the timeout value consistently across
various communication protocols, and always always output the report to
the log file, so that procedures do not have to be locally overridden to
extract this data where needed to reproduce an issue by hand.
* baseboa
The `test_timeout' global parameter is expected to be optionally set by
a board description file and then taken into account by `unix_load' to
override the default of 300. However not only the procedure checks for
the override but it sets the global parameter to the default as well if
not pres
The `test_timeout' global parameter was added with commit 73db65f53795,
however for the `unix' protocol only and then only in the local case.
Update the remote case of the `unix' protocol, other protocols that use
various timeout sources, and the `qemu' board to take any `test_timeout'
setting
Hi,
This patch series spawned as a side effect of our local change to deal
with excessively slow GCC test cases scoring false failures due to hitting
the execution timeout.
To avoid excessive testsuite run times where other test cases do hang, as
it would be the case if the timeout set globa
Move the setting of `testcase_timeout' earlier on in `gdb_comm_load'.
It will be needed for reporting later on. No semantics change.
* config/gdb-comm.exp (gdb_comm_load): Set `testcase_timeout'
earlier on.
---
config/gdb-comm.exp | 13 +++--
1 file changed, 7 insert
12 matches
Mail list logo
