Bug 2038465: Upgrade chromedriver to 90.x to support Mac M1 chips #10691
Conversation
openshift-ci
bot
added
the
needs-ok-to-test
|
Hi @olavtar. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/ok-to-test |
openshift-ci
bot
added
ok-to-test
|
/retest-required |
|
@christianvogt please take a look at this. @spadgett suggested we'd open this PR, but I realize he's out for the year. Not sure why this test is failing. |
olavtar
force-pushed
the
upgrade-chromedriver
branch
from
bea4734
to
5db24e3
Compare
Signed-off-by: Olga Lavtar <olavtar@redhat.com>
olavtar
force-pushed
the
upgrade-chromedriver
branch
from
5db24e3
to
3910c4b
Compare
|
@olavtar Do you mind opening a Bugzilla bug against the Management Console component? We'll need one to make the bot happy. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: olavtar, spadgett The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
olavtar
changed the title
openshift-ci
bot
added
bugzilla/severity-low
|
@olavtar: This pull request references Bugzilla bug 2038465, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
@spadgett I opened a bug: 2038465 but it looks like I can't set the target: expected the bug to target the "4.10.0" release, but it targets "---" instead. Not sure if I have all the same permission to add/edit. Thank you. |
|
/bugzilla refresh Recalculating validity in case the underlying Bugzilla bug has changed. |
|
@openshift-bot: This pull request references Bugzilla bug 2038465, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/bugzilla refresh Recalculating validity in case the underlying Bugzilla bug has changed. |
|
@openshift-bot: This pull request references Bugzilla bug 2038465, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/bugzilla refresh |
openshift-ci
bot
added
the
bugzilla/valid-bug
|
@spadgett: This pull request references Bugzilla bug 2038465, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
openshift-ci
bot
removed
the
bugzilla/invalid-bug
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
@olavtar: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
@olavtar: All pull requests linked via external trackers have merged: Bugzilla bug 2038465 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Chromdriver 77 does not support any chipset other than x64: https://github.com/giggio/node-chromedriver/blob/77.0.0/install.js#L35-L42
upgrade chromedriver version from 77.x to 90.x
Signed-off-by: Olga Lavtar olavtar@redhat.com