tests/run-tests.py: Use TEST_TIMEOUT as timeout for bare-metal tests. #17697
+4
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This TEST_TIMEOUT parameter is already used for PC-based tests (eg unix and webassembly ports), and it makes sense for it to be used for bare-metal ports as well. That way the timeout is configurable for all targets.
Because this increases the default timeout from 10s to 30s, this fixes some long-running tests that would previously fail due to a timeout such as
thread/stress_aes.py
on ESP32.Testing
Tested with ESP32_GENERIC firmware. The
thread/stress_aes.py
test now passes (previously it would fail due to timeout).