[ESM] Fix flaky SQS ReportBatchItemFailures test with proper visiblity timeouts #12323
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.
Motivation
This PR fixes a flaky test with SQS + ESM when the
ReportBatchItemFailures
is set.The duration to poll for an event was too short, meaning re-queued messages had not properly exceeded their visibility timeout -- meaning nothing was re-queued while polling was happening and that the assertion for a non-empty
ReceiveMessage
operation failed, resulting in a test failure.Changes
test_report_batch_item_failures
, ensuring the visibility timeout of the SQS queue is greater than the invocation timeout of the target lambda.Testing