1736583 - Some variants not running against mochitest-browser-chrome

Status: NEW

(Firefox Build System :: Task Configuration, task)

Description

[Andrew Halberstadt [:ahal]]

Upon doing some test config cleanup, I noticed that the socketprocess_networking, webrender-sw-a11y-checks and webrender-sw-wayland variants are configured for mochitest-browser-chrome but are not actually running there. This is because they both fall under the default section and match this line here:
https://searchfox.org/mozilla-central/rev/36aa22c7ea92bd3cf7910774004fff7e63341cf5/taskcluster/ci/test/mochitest.yml#162

Since they are all only configured to run on Linux debug this means that they aren't running.

Comment 1

[Andrew Halberstadt [:ahal]]

Kershaw, do you expect mochitest-browser-chrome to be running with socketprocess_networking? If so you'll need a patch to enable them.

Andrew, do you expect mochitest-browser-chrome to be running with webrender-sw-wayland? If so you'll need a patch to enable them.

Jamie, do you expect mochitest-browser-chrome to be running with webrender-sw-a11y-checks? If so you'll need a patch to enable them.

Note that in all cases I'm only filing this bug to point out the discrepancy. I'm not implying that these variants need to be running on browser-chrome or anything and we can resolve this bug WONTFIX if desired.

Comment 2

[Andrew Halberstadt [:ahal]]

I noticed for webrender-sw-a11y-checks they do run since they define run-on-projects inside the variant definition:
https://searchfox.org/mozilla-central/source/taskcluster/gecko_taskgraph/transforms/tests.py#226

But the other two are still valid questions.

Comment 3

[Kershaw Chang [:kershaw]]

FYI, I filed bug 1741425 for running mochitest-browser-chrome with socketprocess_networking.