Conversation
Test Results - Preflight, Unit23 066 tests - 57 21 175 ✅ - 77 6m 8s ⏱️ -2s Results for commit 3cc349e. ± Comparison against base commit a857a31. This pull request removes 74 and adds 17 tests. Note that renamed tests count towards both.This pull request skips 19 tests.♻️ This comment has been updated with latest results. |
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 49m 8s ⏱️ - 1h 12m 33s Results for commit 3cc349e. ± Comparison against base commit a857a31. This pull request removes 4089 tests.♻️ This comment has been updated with latest results. |
Test Results (amd64) - Integration, Bootstrap 5 files ± 0 5 suites ±0 1h 5m 6s ⏱️ - 1h 35m 43s Results for commit 3cc349e. ± Comparison against base commit a857a31. This pull request removes 4470 tests.♻️ This comment has been updated with latest results. |
Test Results - Alternative Providers180 tests - 1 071 39 ✅ - 671 2m 30s ⏱️ - 28m 35s Results for commit 3cc349e. ± Comparison against base commit a857a31. This pull request removes 1071 tests.♻️ This comment has been updated with latest results. |
Motivation
While working on S3, I had a test interacting with SQS where LocalStack wouldn't shutdown. I tracked it down to CloudWatch re-start its scheduler after it was tasked to shut it down:
We can see that the scheduler is being shutdown then restarted straight away.
I've modified the logic a bit to avoid this issue, and also registered the scheduler to with the shutdown handlers, so that the thread wouldn't block in case something goes wrong when shutting down the service.
Changes
Tests
Test the
tests.aws.services.s3.test_s3_api.TestS3BucketNotificationConfiguration.test_bucket_notification_with_invalid_filter_rulestest with and without this fix.Related