Skip to content
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

Shard e2e test across multiple accounts #1821

Closed
sobolk opened this issue Aug 5, 2024 · 3 comments
Closed

Shard e2e test across multiple accounts #1821

sobolk opened this issue Aug 5, 2024 · 3 comments
Assignees
Labels
flaky Engineering label for flaky tests repo-infrastructure Engineering label for issues related to repo infrastructure tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later testing Engineering label for issues related to tests or test tooling

Comments

@sobolk
Copy link
Member

sobolk commented Aug 5, 2024

We're consistently hitting throttling in some e2e test runs. Which means that we should think about spreading the load of our e2e tests across multiple accounts.

Implementation of this task should include:

  1. Building mechanism to spread traffic across multiple e2e tests accounts.
  2. Building mechanism to manage e2e test accounts via CDK.
  3. Add one additional e2e test account to mitigate current situation.
  4. Solution should be easy to use if we need to add third account in the future.
@sobolk sobolk added tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later testing Engineering label for issues related to tests or test tooling flaky Engineering label for flaky tests repo-infrastructure Engineering label for issues related to repo infrastructure labels Aug 5, 2024
@sobolk sobolk self-assigned this Aug 16, 2024
@sobolk
Copy link
Member Author

sobolk commented Aug 16, 2024

#1879

@sobolk sobolk mentioned this issue Aug 16, 2024
4 tasks
@sobolk
Copy link
Member Author

sobolk commented Aug 16, 2024

Remaining work: canaries.

@sobolk
Copy link
Member Author

sobolk commented Aug 23, 2024

#1902

@sobolk sobolk closed this as completed Aug 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flaky Engineering label for flaky tests repo-infrastructure Engineering label for issues related to repo infrastructure tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later testing Engineering label for issues related to tests or test tooling
Projects
None yet
Development

No branches or pull requests

1 participant