Test errors for out-of-range limit requests

[kainino0x]

See https://crbug.com/1499030

Issue: None

---

Requirements for PR author:

• All missing test coverage is tracked with "TODO" or .unimplemented().
• New helpers are /** documented */ and new helper files are found in helper_index.txt.
• Test behaves as expected in a WebGPU implementation. (If not passing, explain above.)

Requirements for reviewer sign-off:

• Tests are properly located in the test tree.
• Test descriptions allow a reader to "read only the test plans and evaluate coverage completeness", and accurately reflect the test code.
• Tests provide complete coverage (including validation control cases). Missing coverage MUST be covered by TODOs.
• Helpers and types promote readability and maintainability.

When landing this PR, be sure to make any necessary issue status updates.

[kainino0x]

The spec does not actually currently say that 2**32 or 2**53 is an error for alignment limits. I'm proposing it to the spec:
gpuweb/gpuweb#4358

[greggman]

I am confused. The limits tests already test trying to go over the max limit and they all pass.

cts/src/webgpu/api/validation/capability_checks/limits/limit_utils.ts

Line 376 in 41f89e7

const shouldReject = kMinimumLimits.has(limit)

What is the bug this is trying to surface that wasn't already tested?

Can you just add a case there instead of making a new test?

[kainino0x]

What is the bug this is trying to surface that wasn't already tested?

We mishandle values ≥ 2^32 for 32-bit limit types, by static_cast<uint32_t>(uint64_t):
https://chromium-review.googlesource.com/c/chromium/src/+/5002999

Can you just add a case there instead of making a new test?

I may have missed the appropriate test to modify, but I only saw tests that used mul/add and I couldn't easily get specific corner cases in those tests.
I could certainly reduce the number of subcases in this test though.

[greggman]

ok, lgtm 🤷‍♂️

If you wanted to give it a try you could add a new limit here

cts/src/webgpu/api/validation/capability_checks/limits/limit_utils.ts

Line 207 in 41f89e7

export const kMaximumTestValues = ['atLimit', 'overLimit'] as const;

atLimit, overLimit, overStorageSize

but I this fine too I guess. It tests more values.

[kainino0x]

Ack, I think I'll keep this since it can easily test a lot of values. It also does fit in with the tests next to it (even if we have some redundancy between this, those, and the limit_utils based tests).