[test] Disable thread-safety staic analysis on DeviceMutexTest.cpp

Bug: 533405609
Change-Id: Ia43d50b21befc0c48419b69d71a0a8f46a6a6964
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/323395
Auto-Submit: David Neto <dneto@google.com>
Commit-Queue: Alan Baker <alanbaker@google.com>
Reviewed-by: Alan Baker <alanbaker@google.com>
diff --git a/src/dawn/tests/unittests/native/DeviceMutexTests.cpp b/src/dawn/tests/unittests/native/DeviceMutexTests.cpp
index 023134a..470921fc 100644
--- a/src/dawn/tests/unittests/native/DeviceMutexTests.cpp
+++ b/src/dawn/tests/unittests/native/DeviceMutexTests.cpp
@@ -31,14 +31,18 @@
 #include "dawn/platform/DawnPlatform.h"
 #include "gmock/gmock.h"
 #include "gtest/gtest.h"
+#include "src/dawn/common/Compiler.h"
 #include "src/dawn/native/DeviceGuard.h"
 
 namespace dawn::native {
 
 class DeviceMutexTest : public ::testing::Test {
   protected:
-    void Lock(DeviceMutex& mutex) { mutex.Lock(); }
-    void Unlock(DeviceMutex& mutex) { mutex.Unlock(); }
+    // TODO(533405609) Thread safety analysis flags this whole test as
+    // problematic. The issue tracks revisiting the need for a recursive mutex in
+    // the first place.
+    void Lock(DeviceMutex& mutex) DAWN_NO_THREAD_SAFETY_ANALYSIS { mutex.Lock(); }
+    void Unlock(DeviceMutex& mutex) DAWN_NO_THREAD_SAFETY_ANALYSIS { mutex.Unlock(); }
 };
 
 namespace {