Make event invoke function update test more predicatable#12444
Draft
Make event invoke function update test more predicatable#12444
Conversation
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 1h 30m 14s ⏱️ - 21m 13s For more details on these failures, see this check. Results for commit 00d944c. ± Comparison against base commit ccddefd. This pull request removes 1162 tests.♻️ This comment has been updated with latest results. |
Base automatically changed from
fix-flaky-lambda-test-event-retry-reserved-concurrency
to
master
March 28, 2025 15:48
c0ced8a to
00d944c
Compare
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
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.
Note
This test improvement PR is currently blocked by a Lambda parity issue (pending invokes are aborted instead of gracefully finished upon a function update)
Depends on: #12441
Motivation
The test
test_async_invoke_queue_upon_function_updatehas 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-01key 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.