Closed Bug 1900408 Opened 4 months ago Closed 4 months ago

Use CfT chromedriver (Canary or Dev channel) for CaR tests

Categories

(Testing :: Raptor, enhancement, P1)

enhancement

Tracking

(firefox128 fixed)

RESOLVED FIXED
128 Branch
Tracking Status
firefox128 --- fixed

People

(Reporter: kshampur, Assigned: kshampur)

References

(Blocks 3 open bugs)

Details

(Whiteboard: [fxp])

Attachments

(1 file)

Currently we fetch the drivers from here

But it is not clear to me if these are necessarily stable builds or if they are similar to being experimental (like when we used to fetch chromium binaries from here )

Instead it might be more stable for us to use the download from the "last known good version with downloads" json endpoint, using the Canary channel. (I've got a local patch of this working actually for the Stable channel for Bug 1869592, so this could just be as simple as adding the ability to pass channel flags)

A really quick check - in these failures here (which, based on the error log, is an issue with chrome driver starting?) the revision of that fetched chromedriver from the snapshot link is 1309140
but the "last good" canary chromedriver from the json endpoint is 1309068. I would expect there to be some difference between Canary and raw chromium, but given that the major version in the sem ver are the same as CaR, the safest route is probably to use the builds reported as "good" in the end point

(also note to self, print the revision in the fetch log, even though we already save it as a file, it is convenient to just look a the logs)

See Also: → 1890465

(In reply to Kash Shampur [:kshampur] ⌚EST from comment #1)

https://treeherder.mozilla.org/jobs?repo=try&tier=1%2C2%2C3&revision=d9bc0f2330300d649bbda1209d8dd248542f54fa

win/linux seem fine, waiting on intel mac

mac seems to work with this now with the cft driver

Assignee: nobody → kshampur
Status: NEW → ASSIGNED

the OSX failures haven't seem to resolved itself yet upstream, so I am going to work on this asap

Duplicate of this bug: 1900821
Blocks: 1900853
Attachment #9405725 - Attachment description: WIP: Bug 1900408 - Use CfT chromedriver for CaR tests. → WIP: Bug 1900408 - Use CfT chromedriver for CaR tests. r?#perftest
Attachment #9405725 - Attachment description: WIP: Bug 1900408 - Use CfT chromedriver for CaR tests. r?#perftest → Bug 1900408 - Use CfT chromedriver for CaR tests. r?#perftest
Blocks: 1869592
See Also: 1869592
Severity: S3 → S2
Priority: P3 → P1
Pushed by kshampur@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/b700d9b49f9f Use CfT chromedriver for CaR tests. r=perftest-reviewers,taskgraph-reviewers,sparky,bhearsum
Status: ASSIGNED → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → 128 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: