Quibble jobs currently run on stretch, which means they're stuck in Chromium 73, which is rapidly getting out of date.
Buster keeps getting new versions of Chromium (currently 80), so moving to that fixes this problem.
However, we don't want to move the main phpunit/qunit tests away from stretch, as that's what we're running in Wikimedia production.
Consequently, we'll split all repos into selenium and non-selenium jobs, and have the selenium job run on buster, unlike the non-selenium one.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T250513 Split out all selenium test runs into a buster-based job that runs newer Chromium | |||
| Resolved | Jdforrester-WMF | T250514 Create buster-based images for quibble | |||
| Open | None | T254814 Rename all our quibble jobs to make some sense |
Devil: should we use php7.2 (and forward port it to Buster)?
Assuming yes, I filed T250515. Running vanilla php7.3 instead of wmf-custom 7.2 is a bit of a risk.
I'm thinking that rather than adding the buster variants to the already complex naming system for quibble jobs, I'll probably do the systemic renaming work we've discussed before.