From 8a7b9c6ff31aee65fddb7d35bb3806c16e804c25 Mon Sep 17 00:00:00 2001
From: teoxoy <28601907+teoxoy@users.noreply.github.com>
Date: Tue, 16 Jul 2024 14:26:42 +0200
Subject: [PATCH] [tests] delete outdated comment

This was fixed by 6e21f7a9291db4395192d6b510d906978ae2d251.
---
 tests/tests/device.rs | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/tests/tests/device.rs b/tests/tests/device.rs
index e2ed9f5b60..f932faa2f1 100644
--- a/tests/tests/device.rs
+++ b/tests/tests/device.rs
@@ -147,14 +147,6 @@ async fn request_device_error_message() {
 
 // This is a test of device behavior after device.destroy. Specifically, all operations
 // should trigger errors since the device is lost.
-//
-// On DX12 this test fails with a validation error in the very artificial actions taken
-// after lose the device. The error is "ID3D12CommandAllocator::Reset: The command
-// allocator cannot be reset because a command list is currently being recorded with the
-// allocator." That may indicate that DX12 doesn't like opened command buffers staying
-// open even after they return an error. For now, this test is skipped on DX12.
-//
-// The DX12 issue may be related to https://github.com/gfx-rs/wgpu/issues/3193.
 #[gpu_test]
 static DEVICE_DESTROY_THEN_MORE: GpuTestConfiguration = GpuTestConfiguration::new()
     .parameters(TestParameters::default().features(wgpu::Features::CLEAR_TEXTURE))