tests: Add timeout to .gunittest.cfg file #1318
Merged
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.
Also to address a part of #1312.
Adding a default timeout value to .gunittest.cfg in grass-addons too, like for the main repo.
5 minutes is probably not enough because some tests are really long, but I want to see which ones are timing out on the CI runners speed first.
Even though #1314 limited the test step to 45 minutes, the r.futures.calib apparent hang already happens after 7 minutes, so there's almost 40 minutes spent waiting on timing out.