-
Notifications
You must be signed in to change notification settings - Fork 1.3k
CTS failures in limits,maxInterStageShaderVariables for limitTest of underDefault, overMaximum #8945
Copy link
Copy link
Open
Labels
area: ctsIssues stemming from the WebGPU Conformance Test SuiteIssues stemming from the WebGPU Conformance Test Suitetype: bugSomething isn't workingSomething isn't working
Description
The following CTS suites have failures:
webgpu:api,validation,capability_checks,limits,maxInterStageShaderVariables:createRenderPipeline,at_over:limitTest="underDefault";*
webgpu:api,validation,capability_checks,limits,maxInterStageShaderVariables:createRenderPipeline,at_over:limitTest="overMaximum";*
Example failure from underDefault:
[fail] webgpu:api,validation,capability_checks,limits,maxInterStageShaderVariables:createRenderPipeline,at_over:limitTest="underDefault";testValueName="overLimit";async=true;items=["sample_index","sample_mask","sample_mask_out"] (20ms). Log:
- EXPECTATION FAILED: expected actual actualLimit: 15 to equal defaultLimit: 16
at LimitTests.expect (file:///Users/Andy/Development/wgpu/cts/out/common/framework/fixture.js:373:34)
at LimitTests._getDeviceWithSpecificLimit (file:///Users/Andy/Development/wgpu/cts/out/webgpu/api/validation/capability_checks/limits/limit_utils.js:525:18)
at eventLoopTick (ext:core/01_core.js:179:7)
at async LimitTests.testDeviceWithRequestedMaximumLimits (file:///Users/Andy/Development/wgpu/cts/out/webgpu/api/validation/capability_checks/limits/limit_utils.js:647:29)
at async RunCaseSpecific.fn (file:///Users/Andy/Development/wgpu/cts/out/webgpu/api/validation/capability_checks/limits/maxInterStageShaderVariables.spec.js:210:3)
Example failure from overMaximum:
[fail] webgpu:api,validation,capability_checks,limits,maxInterStageShaderVariables:createRenderPipeline,at_over:limitTest="overMaximum";testValueName="overLimit";async=true;items=["sample_index","sample_mask","sample_mask_out"] (18ms). Log:
- EXPECTATION FAILED: DID NOT REJECT
at LimitTests.eventualAsyncExpectation (file:///Users/Andy/Development/wgpu/cts/out/common/framework/fixture.js:258:24)
at LimitTests.shouldReject (file:///Users/Andy/Development/wgpu/cts/out/common/framework/fixture.js:301:10)
at LimitTests.requestDeviceWithLimits (file:///Users/Andy/Development/wgpu/cts/out/webgpu/api/validation/capability_checks/limits/limit_utils.js:445:12)
at LimitTests._getDeviceWithSpecificLimit (file:///Users/Andy/Development/wgpu/cts/out/webgpu/api/validation/capability_checks/limits/limit_utils.js:496:31)
at LimitTests._getDeviceWithRequestedMaximumLimit (file:///Users/Andy/Development/wgpu/cts/out/webgpu/api/validation/capability_checks/limits/limit_utils.js:563:17)
at LimitTests.testDeviceWithRequestedMaximumLimits (file:///Users/Andy/Development/wgpu/cts/out/webgpu/api/validation/capability_checks/limits/limit_utils.js:647:40)
at RunCaseSpecific.fn (file:///Users/Andy/Development/wgpu/cts/out/webgpu/api/validation/capability_checks/limits/maxInterStageShaderVariables.spec.js:210:11)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area: ctsIssues stemming from the WebGPU Conformance Test SuiteIssues stemming from the WebGPU Conformance Test Suitetype: bugSomething isn't workingSomething isn't working
Type
Projects
Status
Todo