Reenable D3D12 test TwoComputeInModule with tint generator

Bug fixed a while back.

Fixed: tint:297
Change-Id: Ia5f2896de10a67309924cdc93e3a73e1abee7a0d
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/47425
Auto-Submit: Ben Clayton <bclayton@google.com>
Commit-Queue: Austin Eng <enga@chromium.org>
Reviewed-by: Corentin Wallez <cwallez@chromium.org>
Reviewed-by: Austin Eng <enga@chromium.org>
This commit is contained in:
Ben Clayton 2021-04-12 17:42:56 +00:00 committed by Commit Bot service account
parent 51edb2b2d0
commit 7799571b50
1 changed files with 0 additions and 4 deletions

View File

@ -66,10 +66,6 @@ TEST_P(EntryPointTests, FragAndVertexSameModule) {
// Test creating two compute pipelines from the same module. // Test creating two compute pipelines from the same module.
TEST_P(EntryPointTests, TwoComputeInModule) { TEST_P(EntryPointTests, TwoComputeInModule) {
// TODO: Reenable once Tint's HLSL writer supports multiple entryPoints on a single stage.
// https://crbug.com/tint/297
DAWN_SKIP_TEST_IF(IsD3D12() && HasToggleEnabled("use_tint_generator"));
wgpu::ShaderModule module = utils::CreateShaderModule(device, R"( wgpu::ShaderModule module = utils::CreateShaderModule(device, R"(
[[block]] struct Data { [[block]] struct Data {
data : u32; data : u32;