Open Bug 1865660 Opened 11 months ago Updated 9 months ago

Determine if we can and should replace chrome release perftests with CfT builds

Categories

(Testing :: Performance, enhancement, P3)

Product:
Testing
Component:
Performance
Type:
enhancement

Tracking

(Not tracked)

People

(Reporter: kshampur, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

(Whiteboard: [fxp])

release/stable chrome-for-testing (cft) builds:

https://googlechromelabs.github.io/chrome-for-testing/#stable

we currently rely on autoupdates for chrome (which is inconsistent on machines) as well as updating our chromedriver fetches every ~4 weeks

this could potentially resolve both with full automation

See Also: → 1864673

One downside is we don't have android CfT builds (it is unclear to me if that is on the roadmap)

Blocks: 1844396
Depends on: 1869592

Just making note I pointed out in Bug 1864673, comment 13 and Bug 1864673, comment 14 that the binaries aren't build with PGO so it wouldn't make sense to replace these (for now)

You need to log in before you can comment on or make changes to this bug.