test: increase timeouts in testStartTransientErrorsWithSuppressionDur… #819
+3
−3
Conversation
This file contains hidden or 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
…ationErrorTermination
mojito317
approved these changes
Jan 30, 2026
ricellis
approved these changes
Jan 30, 2026
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.
What
Increase test timeout from 1s to 4s in
testStartTransientErrorsWithSuppressionDurationErrorTerminationFixes: sdks #1184
Why
The test has tight timing margins (100ms error suppression + jittered backoff retries) that can exceed the 1s timeout under heavy Jenkins load. With randomized backoff delays, the current timeout gives ~1/120 chance of failure. Increasing to 4s reduces this to ~1/1000 while still catching legitimate timing issues.
Test
Green build
PR summary
Fixes: https://github.ibm.com/cloudant/sdks/issues/1184
Note: An existing issue is required before opening a PR.
PR Checklist
Please make sure that your PR fulfills the following requirements:
Angular Commit Message Guidelines.
PR Type
What is the current behavior?
What is the new behavior?
Does this PR introduce a breaking change?
Other information