OK, the issue here isn't about mingw. This is a general issue with mochitest-webgpu and the `run-if = !release_or_beta` condition at the top of the mochitest manifest. The reason it's showing up in the uplift simulations is that mochitest-webgpu only runs on mingw builds on Beta: https://searchfox.org/mozilla-central/rev/8433b62e54fd30663e82f090c4d31554531a2e66/taskcluster/ci/test/mochitest.yml#973 So in general, I think we should rectify what we're telling TC to run vs. what we're telling the harness to run via the test manifest. Jim, can you please add some clarity to that?
Bug 1825785 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
OK, the issue here isn't about mingw. This is a general issue with mochitest-webgpu and the `run-if = !release_or_beta` condition at the top of the mochitest manifest. The reason it's showing up in the uplift simulations is that mingw is the only platform that mochitest-webgpu runs on on Beta: https://searchfox.org/mozilla-central/rev/8433b62e54fd30663e82f090c4d31554531a2e66/taskcluster/ci/test/mochitest.yml#973 So in general, I think we should rectify what we're telling TC to run vs. what we're telling the harness to run via the test manifest. Jim, can you please add some clarity to that?
OK, the issue here isn't about mingw. This is a general issue with mochitest-webgpu and the `run-if = !release_or_beta` condition at the top of the mochitest manifest. The reason it's showing up in the uplift simulations is that mingw is the only platform that mochitest-webgpu runs on on Beta: https://searchfox.org/mozilla-central/rev/8433b62e54fd30663e82f090c4d31554531a2e66/taskcluster/ci/test/mochitest.yml#973 So in general, I think we should rectify what we're telling TC to run vs. what we're telling the harness to run via the test manifest. Jim, can you please add some clarity to that? In general, maybe we should try to clean up the variant scheduling in that `run-on-projects` section.