From 8409a9f82c558c61e2837efdd93204fad065a91d Mon Sep 17 00:00:00 2001 From: Bart <11445373+bthomee@users.noreply.github.com> Date: Thu, 24 Sep 2026 20:49:39 +0200 Subject: [PATCH] docs: Correct the matrix tier the TSan CI config runs in sanitizers.md said the ubuntu-clang-debug-amd64-tsan config runs TSan in the full matrix. The config is flagged "extended" in linux.json, so it runs only on the nightly schedule and on a manual run. Name the tier it is really in, and say what triggers that tier, because the document explains it nowhere else. Co-Authored-By: Claude Opus 5 (1M context) --- docs/build/sanitizers.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/build/sanitizers.md b/docs/build/sanitizers.md index f9a6a02a47..570e8a7bdb 100644 --- a/docs/build/sanitizers.md +++ b/docs/build/sanitizers.md @@ -100,10 +100,11 @@ export TSAN_OPTIONS="include=sanitizers/suppressions/runtime-tsan-options.txt:su More details [here](https://github.com/google/sanitizers/wiki/ThreadSanitizerCppManual). > [!IMPORTANT] -> The `ubuntu-clang-debug-amd64-tsan` CI config runs TSan in the full matrix -> only, and reports nothing back. `runtime-tsan-options.txt` sets -> `halt_on_error=false`, so the run continues past a finding, and the workflow -> appends `exitcode=0` to `TSAN_OPTIONS`, so the finding does not fail the job. +> The `ubuntu-clang-debug-amd64-tsan` CI config runs TSan in the extended matrix +> only, which is the nightly schedule and a manual run, and it reports nothing +> back. `runtime-tsan-options.txt` sets `halt_on_error=false`, so the run +> continues past a finding, and the workflow appends `exitcode=0` to +> `TSAN_OPTIONS`, so the finding does not fail the job. > Both are needed: TSan exits 66 on its own once it has reported anything. Read > the job log to see findings. A test that must fail on one has to run in its own > step with `halt_on_error=1` and `exitcode=66`.