To prevent regressions we need to run the Dawn end2end tests that exercise the GPU backends on the CQ. This should have a respective CI configuration so we can notice when non-Dawn changes break tests.
Running on CI will also be very helpful when Dawn in integrated in Chrome so we can run the WebGPU CTS continuously and catch regressions at the intersection of Dawn and Chrome.
Contrary to ANGLE the plan is to add the Dawn end2end tests to the GPU FYI waterfall and also add fake Dawn-specific bots to the Chromium buildbot jsons so that we can trigger them from Dawn's CQ. Reusing the Chromium FYI bots directly would cause Dawn to run the WebGL CTS and ANGLE tests which are unnecessary.
As a first step, to try to understand all dependencies, the Dawn end2end tests will be added to the Windows NVIDIA configuration. Once that works other configurations will be added too.
Comment 1 by bugdroid1@chromium.org, Nov 6
Project Member