fix: TSan 下跳过 OpenMP 扩展性测试,消除 libomp 运行时误报

ThreadSanitizer 报告 OpenMPScalingTests.ParallelForEfficiency 存在数据
竞争,但竞争双方均在 libomp.so.5 内部(pthread_mutex_lock vs
pthread_mutex_init),属于 OpenMP 运行时与 TSan 的已知不兼容,并非
reduction 本身的真实竞争。在 TSan 下跳过该测试,保留 asan/ubsan 及
同文件其他并发测试的覆盖。

Author: holtwood

tests/property/concurrency_properties.cpp

@@ -450,8 +450,14 @@ TEST(LockFreeQueueTests, EmptyQueuePop) {
  * Validates: Requirements 5.4, 5.5
  */
 TEST(OpenMPScalingTests, ParallelForEfficiency) {
-#ifndef _OPENMP
+#if !defined(_OPENMP)
     GTEST_SKIP() << "OpenMP not available";
+#elif (defined(__has_feature) && __has_feature(thread_sanitizer)) || defined(__SANITIZE_THREAD__)
+    // The OpenMP runtime (libomp) is not TSan-instrumented: its internal
+    // pthread_mutex_init/lock during thread-pool fork-join surface as
+    // false-positive data races. The reduction itself is race-free.
+    GTEST_SKIP() << "OpenMP runtime (libomp) is not TSan-instrumented; "
+                    "internal mutex races are false positives under TSan";
 #else
     constexpr size_t N = 10000000;
     std::vector<double> data(N);