ARCHIVE/rippled
1
0
Fork 0
mirror of https://github.com/XRPLF/rippled.git synced 2026-09-27 15:28:03 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Correct the matrix tier the TSan CI config runs in

Browse Source 
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) <noreply@anthropic.com>
This commit is contained in:
Bart
2026-09-24 20:49:39 +02:00
parent 36d3429a79
commit 8409a9f82c
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/build/sanitizers.md vendored
View File

@@ -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`.