Automate chromedriver (stable) updates
Categories
(Testing :: Performance, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: kshampur, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fxp] )
Although we can't yet use CfT builds to replace our chrome-release tests, this filed bug is to propose/look into a potential "middle ground" of automating just the chromedrivers downloads available from the JSON endpoints here https://googlechromelabs.github.io/chrome-for-testing/#stable
we could add a fetch that always grabs the N latest chromedrivers from the endpoint (or just singular, latest, so that we are forced to just maintain one e.g. bug 1860044)
Also if checksum is a concern, this was brought up https://github.com/GoogleChromeLabs/chrome-for-testing/issues/70#issuecomment-1822476957
so should be safe?
One thing to note is Autoupdates are not reliable. And doesn't happen at all for Macs (relevant, bug 1841106, comment 3)
But this bug could be a good step forward for this
Updated•7 months ago
|
Comment 1•7 months ago
|
||
Regarding checksums, something that wasn't mentioned in the issue you linked is that they provide us with a way of verifying that the download wasn't corrupted from network errors (or other errors), but I don't think it's a big concern or blocker for us.
Comment 2•5 months ago
|
||
In bug 1876822, Jeff suggests running \Program Files (x86)\Google\Update\GoogleUpdate.exe /ua /installsource scheduler
to force checking for updates before running the test.
Reporter | ||
Comment 3•5 months ago
•
|
||
rcurran confirmed mac auto updates are enabled. So it seems linux + mac are good, but windows and android seem to be lagging by 1-2 versions according to redash and also just checking mozilla-central on treeherder
So the automation we could implement here is just to always grab the 2 latest chromedrivers (2 to be safe) using the CfT json endpoints
Reporter | ||
Comment 4•2 months ago
|
||
rewording this task. it was determined that we can do it. And I think we should do it at some point. I've added the perftest triage white board as I'd like to potentially re groom this/ discuss again in perftest triage
Reporter | ||
Comment 5•2 months ago
|
||
removing perftest:triage tag, as we decided we will do this sometime Q2/Q3
Reporter | ||
Updated•26 days ago
|
Reporter | ||
Comment 6•3 days ago
|
||
thought: we can continue to manually update windows chromedriver as that is the one platform that is having issues with auto update, and instead automate linux/mac.
best way would be to expand this script https://searchfox.org/mozilla-central/rev/56dd89bcf4d3b85f66621e89eac6e2936ad382d9/taskcluster/scripts/misc/fetch-cft-chromedriver.py to accommodate a channel flag (defaults to canary). We'd use the stable flag for this and only do it for non-win platforms
Description
•