Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Report PRECONDITION_FAILED-ish outcomes for unavailable optional features #3859

Open
ErichDonGubler opened this issue Jul 12, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@ErichDonGubler
Copy link
Member

Quite a few tests in CTS exercise optional features in the WebGPU spec. When these tests' feature dependencies are not satisfied, they currently report PASS (IME; this may be incorrect, viz., some may yield FAIL instead).

According to WPT upstream's "Optional features" section, tests of optional features (i.e., the shader-f16 feature) should use the assert_implements_optional API to emit an PRECONDITION_FAILED outcome. This seems an interesting distinction not only for WPT, but also for the standalone runner's reports.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant