Make event invoke function update test more predicatable #12444
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.
Depends on: #12441
Motivation
The test
test_async_invoke_queue_upon_function_update
has been flaky in CircleCI (e.g., old example) and locally (assertion error14 != 15
).Changes
TODO
It seems that the SQS message does not get deleted properly although the delete_message call was successful 🤔 .The same test passes against AWS.sqs_create_queue(Attributes={"VisibilityTimeout": "90"})
(the default 20s should be ok as long as the cold start doesn't take more than 10s)sleep-01
key appears multiple times because the initial invoke is aborted with the update instead of continuted and then the retry triggers another invoke. To fix this, Lambda should not abort pending invokes upon function update.