Maintenance: E2E tests are flaky

[rubenfonseca]

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

• This request meets Lambda Powertools Tenets
• Should this be considered in other Lambda Powertools languages? i.e. Java, TypeScript

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.

[github-actions]

This is now released under 2.7.1 version!