You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm finding that it would be nice to be able to use wildcards in queries. For example i'd like to test all the texture builtins with webgpu:shader,execution,expression,call,builtin,texture*
I haven't looked into what it would take to make that work or if there is some concrete reason to disallow it.
I get that one issue is the harness doesn't know all the tests since it only loads what's in the query but, IDK, maybe the server/build could have a list of tests and if the query doesn't fit the current rules it could load the full list and do a glob
The text was updated successfully, but these errors were encountered:
I don't think there's any specific reason we couldn't support that. Unfortunately there's a fair bit of code that relies on the current query structure though.
I'm finding that it would be nice to be able to use wildcards in queries. For example i'd like to test all the texture builtins with
webgpu:shader,execution,expression,call,builtin,texture*
I haven't looked into what it would take to make that work or if there is some concrete reason to disallow it.
I get that one issue is the harness doesn't know all the tests since it only loads what's in the query but, IDK, maybe the server/build could have a list of tests and if the query doesn't fit the current rules it could load the full list and do a glob
The text was updated successfully, but these errors were encountered: