[tools][cts] Make tags less explicit
Changes how the CTS roller generates expectations for failing tests.
Previously, the most explicit tags were used. Now, the least explicit
tags from several core tag sets (OS, GPU, device) are used. The old
behavior is still available behind the --generate-explicit-tags flag.
This is almost guaranteed to generate expectations which are overly
broad, but the unexpected pass finder will be used to automatically
narrow expectations to the configurations that actually need them.
This CL also includes the following changes to the expectation files:
* Auto-generated expectations have their tags simplified in accordance
with the CTS roller changes
* Skip expectations moved into permanent/temporary Skip expectations
to make it clearer which should be fixed vs. left alone
* Old CTS roller annotations removed since the simplified code path
is here to stay
Bug: 388307199
Change-Id: I37164c1d6c7e533bf3cc6719e1566f2d8ef3b6e6
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/221859
Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Commit-Queue: Brian Sheedy <bsheedy@google.com>
Reviewed-by: dan sinclair <dsinclair@chromium.org>
Dawn is an open-source and cross-platform implementation of the WebGPU standard. More precisely it implements webgpu.h that is a one-to-one mapping with the WebGPU IDL. Dawn is meant to be integrated as part of a larger system and is the underlying implementation of WebGPU in Chromium.
Dawn provides several WebGPU building blocks:
webgpu.h version that Dawn implements.webgpu.h.Helpful links:
Developer documentation:
User documentation: (TODO, figure out what overlaps with the webgpu.h docs)
BSD 3-Clause License, please see LICENSE.
This is not an officially supported Google product.