Skip to content

Maintenance: address integration test flakiness #1668

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.

Sign up for GitHub

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

Jump to bottom
Closed
1 of 2 tasks
dreamorosi opened this issue Sep 3, 2023 · 1 comment · Fixed by #1669
Closed
1 of 2 tasks

Maintenance: address integration test flakiness #1668

dreamorosi opened this issue Sep 3, 2023 · 1 comment · Fixed by #1669
Assignees
@dreamorosi
Labels
completed This item is complete and has been merged/shipped internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)

Comments

@dreamorosi
Copy link
Contributor

Summary

In #1661 we have made significant changes in the integration test infrastructure, we have however introduced some transient failures due to the naming of some resources.

Before moving onto new areas we should address this.

Why is this needed?

So that the tests can be run consistently.

Which area does this relate to?

Tests

Solution

No response

Acknowledgment

Future readers

Please react with 👍 and your use case to help us understand customer demand.
@dreamorosi dreamorosi added internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) confirmed The scope is clear, ready for implementation labels Sep 3, 2023
@dreamorosi dreamorosi self-assigned this Sep 3, 2023
@dreamorosi dreamorosi linked a pull request Sep 3, 2023 that will close this issue
chore(tests): address integration test flakiness #1669
Merged
9 tasks
@github-project-automation github-project-automation bot moved this from Working on it to Coming soon in Powertools for AWS Lambda (TypeScript) Sep 4, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Sep 4, 2023

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues 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.

@dreamorosi dreamorosi moved this from Coming soon to Shipped in Powertools for AWS Lambda (TypeScript) Sep 4, 2023
@dreamorosi dreamorosi added completed This item is complete and has been merged/shipped and removed confirmed The scope is clear, ready for implementation labels Sep 4, 2023
@dreamorosi dreamorosi mentioned this issue Sep 4, 2023
Merged
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dreamorosi dreamorosi

Labels
completed This item is complete and has been merged/shipped internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Projects
Powertools for AWS Lambda (TypeScript)
Status: Shipped
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore(tests): address integration test flakiness aws-powertools/powertools-lambda-typescript
1 participant
@dreamorosi