-
Notifications
You must be signed in to change notification settings - Fork 521
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
fix(examples): fix architect example on m1 #3447
Conversation
ccbba76
to
b55e06a
Compare
b55e06a
to
fb0cac2
Compare
@@ -9,8 +9,8 @@ | |||
|
|||
## IMPORTANT | |||
# If you change the `default_docker_image` version, also change the `cache_key` version | |||
var_1: &default_docker_image circleci/node:12.18.3 | |||
var_2: &browsers_docker_image circleci/node:12.18.3-browsers | |||
var_1: &default_docker_image circleci/node:12.22.7 |
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.
This is a version of node which supports m1?
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.
The architect e2e rule relies on host's version of chrome. In order for ci to pass I need a matching chrome version in package.json and whatever this docker container contains.
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.
The version of chrome in the previous container version didn't have an m1 release.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The angular architect example is broken on m1. The version of webdriver-manager that was being used had a bug that prevented it from finding the correct url to download chrome drivers on an m1 architecture.
What is the new behavior?
Resolved the correct version of webdriver-manager and updated e2e tests to run using an m1-supported version of chrome.
Does this PR introduce a breaking change?
Other information