Skip to content

build: fix e2e tests failing due to chromedriver release #14461

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

Merged

Conversation

devversion
Copy link
Member

@devversion devversion commented Dec 11, 2018

Apparently the webdriver-manager always uses the latest version of the chromedriver. This is problematic because the CI does not always use the latest chrome version that works with the chromedriver from webdriver-manager.

In order to fix this, we lock the webdriver manager version to a specific version. Similarly to how it's done for angular/angular.

Note that this also restricts which Chrome versions can be run locally with the e2e tests, but the chromedriver range seems to always cover at least the latest two versions (which works for us)

@devversion devversion requested a review from jelbourn as a code owner December 11, 2018 10:55
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Dec 11, 2018
@devversion devversion added pr: merge safe target: patch This PR is targeted for the next patch release labels Dec 11, 2018
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Dec 11, 2018
@mmalerba mmalerba merged commit 1124dc2 into angular:master Dec 11, 2018
@devversion devversion deleted the build/update-circle-browser-image branch December 11, 2018 19:27
devversion added a commit to devversion/material2 that referenced this pull request Dec 11, 2018
Apparently the webdriver-manager always uses the _latest_ version of the chromedriver. This is problematic because the CI does not always use the latest chrome version that _works_ with the chromedriver from `webdriver-manager`.

In order to fix this, we lock the webdriver manager version to a specific version. Similarly to how it's done for `angular/angular`.

Note that this also restricts which Chrome versions can be run locally with the e2e tests, but the chromedriver range seems to always cover at least the latest two versions (which works for us)
mmalerba pushed a commit that referenced this pull request Dec 11, 2018
…4475)

Apparently the webdriver-manager always uses the _latest_ version of the chromedriver. This is problematic because the CI does not always use the latest chrome version that _works_ with the chromedriver from `webdriver-manager`.

In order to fix this, we lock the webdriver manager version to a specific version. Similarly to how it's done for `angular/angular`.

Note that this also restricts which Chrome versions can be run locally with the e2e tests, but the chromedriver range seems to always cover at least the latest two versions (which works for us)
josephperrott pushed a commit to josephperrott/components that referenced this pull request Jan 14, 2019
Apparently the webdriver-manager always uses the _latest_ version of the chromedriver. This is problematic because the CI does not always use the latest chrome version that _works_ with the chromedriver from `webdriver-manager`.

In order to fix this, we lock the webdriver manager version to a specific version. Similarly to how it's done for `angular/angular`.

Note that this also restricts which Chrome versions can be run locally with the e2e tests, but the chromedriver range seems to always cover at least the latest two versions (which works for us)
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants