Skip to content

armgit / laya

Public Imported from GitHub
0

Non-autoregressive System 1 decision engine. Typed choice, score and yes/no decisions over any text in a single forward pass, in 100+ languages, with a router that picks the right checkpoint per request.

ci(cpp): ignore the uninstrumented module instead of suppressing the library

Nandakishor7135bb82402c
diff --git a/laya-cpp/tsan-onnxruntime.supp b/laya-cpp/tsan-onnxruntime.supp
deleted file mode 100644
index 79cecbb2..00000000
--- a/laya-cpp/tsan-onnxruntime.supp
+++ /dev/null
@@ -1,24 +0,0 @@
-# ThreadSanitizer suppressions for the prebuilt ONNX Runtime.
-#
-# laya-cpp links the official ONNX Runtime binary that cmake/onnxruntime.cmake downloads and
-# sha256-verifies. That library is not built with -fsanitize=thread, so TSan cannot see its
-# internal synchronization: the happens-before edges its own mutexes and atomics establish are
-# invisible, and every buffer its intra-op thread pool hands back to the main thread therefore
-# looks like an unsynchronized access.
-#
-# Measured, not assumed: the `onnx (clang++, tsan)` job reported 342 races, every single one with
-# a libonnxruntime.so frame, and all of them in `memcpy` or `operator delete`. 20 of 479 tests
-# failed as a result, including four that only assert the static-holder helper's exit status and
-# saw TSan's own exitcode=66.
-#
-# Scope, and what it costs. `called_from_lib` drops a report only when the accessing stack runs
-# inside this library, so a race between two laya threads on laya-owned state is still reported.
-# What it does give up is a race where laya hands memory to an ONNX Runtime worker thread, since
-# that thread's stack is inside the library. TSan cannot adjudicate those either way while the
-# library is uninstrumented, so the choice is between suppressing them and switching the whole
-# cell off; this keeps the laya-vs-laya coverage the cell exists for, which is what
-# OnnxRig.ConcurrentPredictAgreesWithASerialCall and CloseInterruptsARunInFlight exercise.
-#
-# Revisit if ONNX Runtime ever ships a TSan-instrumented build, or if laya starts passing a
-# callback into the library.
-called_from_lib:libonnxruntime.so