-
Notifications
You must be signed in to change notification settings - Fork 4k
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
chore: remove invalid test #17337
chore: remove invalid test #17337
Conversation
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Follow up on #17337 to fix regression suites. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Follow up on #17337 to fix regression suites. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Follow up on aws#17337 to fix regression suites. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
The test in question can never succeed under the current test circumstances.
Followoing #17298, all our accounts are bootstrapped with the modern bootstrap stack, which makes it so that if
newStyleSynthesis
apps are deployed to it, it will always use that modern stack, and ignore the--toolkit-stack-name
.In order for this test to pass, we must have at least one account that is bootstrapped with the legacy stack, and we must match this test to run on that account.
This doesn't seem to be worth the effort at this point, since this test was focused mainly around migration from legacy to modern bootstrap stacks, and we are probably passed that point by now.
Having said that, taking a note to re-evaluate this decision in our ops meeting next week, but for now I don't think its worth blocking the release over.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license