test: extend e2e test timeout for Amazon Q feature dev multi-iteratio… #7201
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
/runIntegrationTests |
Contributor
Author
|
FeatureDev E2E only run in |
Contributor
Author
|
/retryBuilds |
neilk-aws
approved these changes
Apr 30, 2025
Contributor
Author
|
/runIntegrationTests |
Contributor
Author
|
/runIntegrationTests |
Contributor
Author
|
It looks the test timeout in master as well. https://d1ihu6zq92vp9p.cloudfront.net/96d2fe6f-ecce-4741-a45a-1c4038771295/report.html |
justinmk3
reviewed
May 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
The default 5-minute timeout was insufficient for Amazon Q Feature Dev tests that involve code generation with multiple iterations. This was causing tests to fail prematurely before they could complete their full execution cycle.
Solution
Extended the test timeout to 15 minutes (900,000ms) specifically for the code generation test with multi-iteration scenarios. This provides adequate time for multi-iteration code generation tests to complete their execution while maintaining the existing test behavior.
feature/xbranches will not be squash-merged at release time.