Skip to content

[EKS] Separating concurrency tag to be per region #37

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
Apr 9, 2024

Conversation

majanjua-amzn
Copy link
Contributor

In the current state, if an EKS E2E test in a single region runs long then all regions will not be able to proceed until that one region is done running its test. This creates cross-region dependencies on our E2E test canary despite them being hosted on entirely separate infrastructure, and can cause false alarms to go off in all regions. As such, I've moved the concurrency tag accordingly and added the region to it so there is no interference

Description of changes:

  • Remove concurrency tag from the job that generates the test matrix
  • Add concurrency tag to the test itself with the region in the group attribute

Testing:
I do not have the infrastructure set up in my personal fork/account to run this commit as a canary, but I ran the workflows in the following commits twice to show the logic is functional and when checking the workflow runs the one that started second did wait for the first to complete appropriately and only at a regional level. Commits:
Commit 1: link
Commit 2: link
Screenshot 2024-04-09 at 1 41 58 PM
Screenshot 2024-04-09 at 1 41 51 PM

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@majanjua-amzn majanjua-amzn added the enhancement New feature or request label Apr 9, 2024
@majanjua-amzn majanjua-amzn requested review from vastin and harrryr April 9, 2024 20:55
@majanjua-amzn majanjua-amzn self-assigned this Apr 9, 2024
Copy link
Contributor

@vastin vastin left a comment

Choose a reason for hiding this comment

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

LGTM. ty.

@majanjua-amzn majanjua-amzn merged commit 9a6e0cb into main Apr 9, 2024
@zzhlogin zzhlogin deleted the eks-concurrency branch June 6, 2024 18:14
zzhlogin pushed a commit to zzhlogin/aws-application-signals-test-framework that referenced this pull request Jun 6, 2024
…ncurrency

[EKS] Separating concurrency tag to be per region
zzhlogin pushed a commit to zzhlogin/aws-application-signals-test-framework that referenced this pull request Jun 6, 2024
…ncurrency

[EKS] Separating concurrency tag to be per region
zzhlogin pushed a commit to zzhlogin/aws-application-signals-test-framework that referenced this pull request Jun 6, 2024
…ncurrency

[EKS] Separating concurrency tag to be per region
zzhlogin pushed a commit to zzhlogin/aws-application-signals-test-framework that referenced this pull request Jun 6, 2024
…ncurrency

[EKS] Separating concurrency tag to be per region
georgeboc pushed a commit to georgeboc/aws-application-signals-test-framework that referenced this pull request Jul 8, 2024
)

*Description of changes:*
Implement Unit Test for Metric Attribute Generator

By submitting this pull request, I confirm that you can use, modify,
copy, and redistribute this contribution, under the terms of your
choice.

---------

Co-authored-by: ADOT Patch workflow <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants