Only try OOM allocation size with 'absurd' value (#4489) The current value version of the OOM allocation causes issues with machines that have more than 128GB of RAM. Since one of the values it tries to test is 128GB. This change removes this lower value, leaving the higher value kMaxSafeMultipleOf8, which is ~8,192TB. I am aware of no commercially available machine supports anything near this much RAM, so this should be good for the foreseeable future. If there is a device in the future with this much RAM, hopefully Number will have been re-specified to something like a float128 by then. Fixes #4488
This is the conformance test suite for WebGPU. It tests the behaviors defined by the WebGPU specification.
The contents of this test suite are considered normative; implementations must pass them to be WebGPU-conformant. Mismatches between the specification and tests are bugs.
This test suite can be embedded inside WPT or run in standalone.
Please read the introductory guidelines before contributing. Other documentation may be found in docs/ and in the helper index (source).
Read CONTRIBUTING.md on licensing.
For realtime communication about WebGPU spec and test, join the #WebGPU:matrix.org room on Matrix.