Skip to content

Conversation

shivakunv
Copy link
Contributor

@shivakunv shivakunv commented Sep 6, 2025

Sometimes ,new kernel releases or enabling full fledged e2e AWS testing , creates too many instances ( >= 12) . This change will restrict AWS instances to batches of 5 . Once a batch of 5 completes , another batch of upto 5 instances will be created to continue running the e2e tests .
This will resolve AWS account instance limit error ( vpcs creation)

@shivakunv shivakunv self-assigned this Sep 6, 2025
@shivakunv shivakunv force-pushed the limite2einstance branch 2 times, most recently from a17a71b to 24f7593 Compare September 7, 2025 14:32
Signed-off-by: Shiva Kumar (SW-CLOUD) <[email protected]>
@shivakunv
Copy link
Contributor Author

@tariq1890 @cdesiniotis PTAL
@ArangoGutierrez Batch e2e instance (max 5)

@shivakunv shivakunv changed the title limit e2e instance Restrict e2e runs to 5 instances Sep 8, 2025
@tariq1890
Copy link
Contributor

@shivakunv Please provide more context in the pull request's description

@shivakunv
Copy link
Contributor Author

@shivakunv Please provide more context in the pull request's description

updated the description

@shivakunv
Copy link
Contributor Author

@tariq1890
Sometimes ,new kernel releases or enabling full fledged e2e AWS testing , creates too many instances ( >= 12) . This change will restrict AWS instances to batches of 5 . Once a batch of 5 completes , another batch of upto 5 instances will be created to continue running the e2e tests .
This will resolve AWS account instance limit error ( vpcs creation)

@shivakunv
Copy link
Contributor Author

@tariq1890 @cdesiniotis PTAL

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants