Open
Bug 1814098
Opened 2 years ago
Updated 7 months ago
WebGPU CTS: incorrect exception type in `webgpu:api,operation,adapter,requestDevice:limits,unknown:` test case
Categories
(Core :: Graphics: WebGPU, defect, P2)
Core
Graphics: WebGPU
Tracking
()
NEW
People
(Reporter: ErichDonGubler, Unassigned)
References
(Blocks 2 open bugs, Regression)
Details
(Keywords: regression)
The webgpu:api,operation,adapter,requestDevice:limits,unknown: test case yields this output:
EXPECTATION FAILED: THREW NotSupportedError, instead of OperationError: NotSupportedError: Unable to instantiate a Device
eventualAsyncExpectation@https://gpuweb.github.io/cts/out/common/framework/fixture.js:203:24
shouldReject@https://gpuweb.github.io/cts/out/common/framework/fixture.js:242:10
@https://gpuweb.github.io/cts/out/webgpu/api/operation/adapter/requestDevice.spec.js:134:5
|
Reporter | |
Updated•2 years ago
|
Blocks: webgpu-v1-cts-blockers
|
|
Reporter | |
Updated•2 years ago
|
No longer blocks: webgpu-cts
Regressed by: webgpu-cts
|
||
Updated•2 years ago
|
Keywords: regression
|
|
||
Comment 1•2 years ago
|
||
The severity field is not set for this bug.
:jimb, could you have a look please?
For more information, please visit auto_nag documentation.
Flags: needinfo?(jimb)
|
|
Reporter | |
Updated•1 year ago
|
Priority: -- → P2
|
||
Updated•7 months ago
|
Blocks: webgpu-triage
You need to log in
before you can comment on or make changes to this bug.
Description
•