1821378 - Add ARM chrome driver to our existing fetches

Status: RESOLVED FIXED

(Testing :: Raptor, task, P1)

Description

[Kash Shampur [:kshampur] ⌚EST]

Once Bug 1808636 is done, we'd probably need to make use of the Mac ARM chromedriver for M1's if we wish to run chrome tests on these machines

e.g. for v111, https://chromedriver.storage.googleapis.com/index.html?path=111.0.5563.64/, the 3rd link in the list

Comment 1

[Kash Shampur [:kshampur] ⌚EST]

just a note that since chromedriver 115 e.g. in Bug 1835383, it has been changed slightly the way to fetch the chrome drivers.

Comment 2

[Kash Shampur [:kshampur] ⌚EST]

:andrej this may resolve the timeout issues on the m2

Comment 3

[Kash Shampur [:kshampur] ⌚EST]

Here is some potential supporting evidence that this could help with the long test times https://github.com/titusfortner/webdrivers/issues/191#issuecomment-752960601

Comment 4

[Andrej (:aglavic)]

Attachment: Bug 1821378 - Add ARM chromedriver to existing fetch tasks for macosx. r?#perftest

Recently we added Mac OSX with apple silicon, the chromedrivers used for apple silicon are different than the ones used for non-apple silicon chips
In this patch I add the ability to use differnt chromedrivers for mac by modifying the extracted names section which is where we untar the zipped chromedriver

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/a151165c8ba1
Add ARM chromedriver to existing fetch tasks for macosx. r=perftest-reviewers,taskgraph-reviewers,kshampur,gbrown

Comment 6

[Cosmin Sabou [:CosminS]]

https://hg.mozilla.org/mozilla-central/rev/a151165c8ba1