Thanks to visit codestin.com
Credit goes to github.com

Skip to content

test(esm/sqs): Skip flaky test_report_batch_item_failures test #12713

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

Merged
merged 1 commit into from
Jun 4, 2025

Conversation

gregfurman
Copy link
Contributor

Motivation

This test makes a faulty assumption that a ReceiveMessages call will always return a value. Skip for now but re-visit this test after release.

Changes

  • Skips flaky tests/aws/services/lambda_/event_source_mapping/test_lambda_integration_sqs.py/test_report_batch_item_failures

@gregfurman gregfurman added this to the 4.5 milestone Jun 4, 2025
@gregfurman gregfurman self-assigned this Jun 4, 2025
@gregfurman gregfurman added semver: patch Non-breaking changes which can be included in patch releases aws:lambda:event-source-mapping AWS Lambda Event Source Mapping (ESM) labels Jun 4, 2025
@gregfurman gregfurman requested review from tiurin and anisaoshafi June 4, 2025 15:58
Copy link

github-actions bot commented Jun 4, 2025

Test Results - Preflight, Unit

21 595 tests  ±0   19 940 ✅ +1   6m 20s ⏱️ -13s
     1 suites ±0    1 655 💤 ±0 
     1 files   ±0        0 ❌  - 1 

Results for commit 9563c88. ± Comparison against base commit 9692260.

Copy link
Member

@joe4dev joe4dev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good decision to skip 👍

@@ -538,6 +541,7 @@ def test_report_batch_item_failures(
# now wait for the first invocation result which is expected to have processed message 1 we wait half the retry
# interval to wait long enough for the message to appear, but short enough to check that the DLQ is empty after
# the first attempt.
# FIXME: We cannot assume that the queue will always return a message in the given time-interval.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe, we can use the collect sqs messages fixture doing retries. Good catch 👍

Copy link

github-actions bot commented Jun 4, 2025

Test Results (amd64) - Acceptance

7 tests   5 ✅  3m 5s ⏱️
1 suites  2 💤
1 files    0 ❌

Results for commit 9563c88.

Copy link

github-actions bot commented Jun 4, 2025

Test Results - Alternative Providers

986 tests   568 ✅  22m 23s ⏱️
  4 suites  418 💤
  4 files      0 ❌

Results for commit 9563c88.

@anisaoshafi anisaoshafi merged commit 426eeed into master Jun 4, 2025
50 of 52 checks passed
@anisaoshafi anisaoshafi deleted the test/esm/skip-flaky-esm-sqs branch June 4, 2025 16:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aws:lambda:event-source-mapping AWS Lambda Event Source Mapping (ESM) semver: patch Non-breaking changes which can be included in patch releases
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants