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

Move builtin must_use tests into per-builtin validation suites #3502

Closed
jrprice opened this issue Mar 14, 2024 · 1 comment · Fixed by #3745
Closed

Move builtin must_use tests into per-builtin validation suites #3502

jrprice opened this issue Mar 14, 2024 · 1 comment · Fixed by #3745
Assignees
Labels

Comments

@jrprice
Copy link
Contributor

jrprice commented Mar 14, 2024

We have tests that the results of most builtins must be used in must_use.spec.ts, but we have also started adding equivalent tests inside the per-builtin validation suites, e.g. #3496.

We should probably move all of these must_use tests into the per-builtin suites to make it clearer what should be covered when adding a new builtin. The dedicated must_use suite would then focus on user-specified @must_use attributes.

@alan-baker
Copy link
Contributor

Don't neglect src/webgpu/shader/validation/expression/call/builtin/value_constructor.spec.ts.

alan-baker added a commit to alan-baker/webgpu-cts that referenced this issue May 14, 2024
Fixes gpuweb#3502

* Moves must_use tests for builtin functions to specific files
alan-baker added a commit to alan-baker/webgpu-cts that referenced this issue May 15, 2024
Fixes gpuweb#3502

* Moves must_use tests for builtin functions to specific files
alan-baker added a commit that referenced this issue May 15, 2024
Fixes #3502

* Moves must_use tests for builtin functions to specific files
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants
@jrprice @dneto0 @alan-baker and others