-
Notifications
You must be signed in to change notification settings - Fork 77
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
test: improve E2E test reliability #2269
Conversation
Fixes deployment errors due to unsupported Node14 Lambda runtime in custom resource provider in CDK v2.80.0
stripColors: true, | ||
env, | ||
disableCIDetection: s.disableCIDetection, | ||
noOutputTimeout: 10 * 60 * 1000, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does init
take 10 minutes? Searchable tests may need longer timeouts too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's keep an eye on that -- I'm not seeing failures in searchable tests, so it may be that I am barking up the wrong tree entirely.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Searchable tests usually takes longer time during amplify push
which was resolved previously. The init process time should stay the same as the others
Description of changes
Checklist
yarn test
passesBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.