Increasing timeouts for linter tests #429
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.
r? @etsai-stripe
These tests have been intermittently failing due to timeouts: https://github.com/stripe/vscode-stripe/runs/4121204401?check_suite_focus=true
The open and show document functions can take a couple of seconds in the worst case scenario which will cause the test to timeout (the default is 2 seconds). Even for ones that do pass, we always come close to the timeout in the first two test cases.
See logs added here: https://github.com/stripe/vscode-stripe/runs/4159081815?check_suite_focus=true.