-
Notifications
You must be signed in to change notification settings - Fork 427
Maintenance: E2E tests are flaky #1877
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
Labels
tech-debt
Technical Debt tasks
Comments
7 tasks
7 tasks
7 tasks
|
This is now released under 2.7.1 version! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
After the last batch of fixes, the E2E tests are still flaky.
For instance awslabs/aws-lambda-powertools-python/actions/runs/4047838730/jobs/6962344909 failed with a logging not getting enough messages.
Other times, it seems the whole setup fails for unknown reasons: awslabs/aws-lambda-powertools-python/actions/runs/4047900294
Why is this needed?
To have confidence in our E2E tests
Which area does this relate to?
Tests
Solution
No response
Acknowledgment
The text was updated successfully, but these errors were encountered: