Raise timeout in t/debugger.t (RT#117107) #131
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The "debugger" test in t/debugger.t currently sets `alarm 5` which leads to reproducible failures on slow platforms like the Raspberry Pi 1. In practice the test can take over 10 seconds; setting the timeout to `30` should give plenty of wiggle room while still not blocking the whole tests for too long in case of failures. Fixes: RT#117107
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The "debugger" test in t/debugger.t currently sets
alarm 5which leads to reproducible failures on slow platforms like the Raspberry Pi 1. In practice the test can take over 10 seconds; setting the timeout to30should give plenty of wiggle room while still not blocking the whole tests for too long in case of failures.Fixes: RT#117107