-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
test(esm/sqs): Skip resource intensive flaky SQS message override test #12681
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for being proactive, Greg 🚀
Test Results - Alternative Providers597 tests 420 ✅ 15m 0s ⏱️ Results for commit 5b985f7. |
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 1h 19m 11s ⏱️ - 22m 59s Results for commit 5b985f7. ± Comparison against base commit e10e769. This pull request removes 1209 tests.
This pull request skips 1 test.
|
Test Results (amd64) - Integration, Bootstrap 5 files 5 suites 2h 21m 15s ⏱️ Results for commit 5b985f7. |
Motivation
The case of reading 10 000 records in a single SQS call was made possible via a custom override header. While the functionality works, this is a resource intensive task requiring 10K records to be read into SQS, followed by invocations of a target lambda of up to 2.5K records at a time.
Hence, this test should only be run on particular runners that better cater for these memory/compute requirements.
Changes
TEST_PERFORMANCE
environment variable is set.