1794612 - Chrome binary for arm64 changed back to _m1

Status: RESOLVED INVALID

(Testing :: web-platform-tests, defect)

Description

[James Graham [:jgraham]]

https://chromedriver.storage.googleapis.com/ shows some files with the _m1 suffix and some with the _arm64 suffix. I guess Google reverted a change on their side when it broke something. We should at least revert the change in bug 1793801, and consider updating the code to allow both suffixes.

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+1]]

FYI I've also asked Maksim if he is aware of that: https://github.com/web-platform-tests/wpt/pull/36291#issuecomment-1274860435

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1793801

Comment 3

[sadym]

The _m1 prefix was changed to _arm64 since chrome version 106, and is not planned to be changed afterwards.

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+1]]

To add chromedriver 107 still has mac_arm64:
https://chromedriver.storage.googleapis.com/index.html?path=107.0.5304.18/

James, maybe you only checked the entries at the top which start with releases around the version number 100?

I assume that we can close this bug?

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1793801