Repository navigation
Fix TSan CI build for develop, cantera - #2991
Merged
Merged
Conversation
… ASLR entropy Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
bigfooted
force-pushed
the
fix_cantera_tsan
branch
from
October 23, 2026 11:09
c147a9f to
d1b8ac8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed Changes
The "FATAL: ThreadSanitizer: unexpected memory mapping" message comes from the TSan runtime. It happens when the kernel's ASLR randomization is too high for TSan's fixed shadow-memory layout (vm.mmap_rnd_bits=32). That is the default on recent GitHub runner images and kernels.
The failing step is the bootstrap of ninja, because the Cantera subproject builds its own ninja when none is on the PATH. The TSan flags from the job are inherited by that bootstrap. The freshly built ./ninja is therefore TSan-instrumented and dies on startup with exit status 66, which gives the Python traceback you see.
Related Work
Resolve any issues (bug fix or feature request), note any related PRs, or mention interactions with the work of others, if any.
PR Checklist
Put an X by all that apply. You can fill this out after submitting the PR. If you have any questions, don't hesitate to ask! We want to help. These are a guide for you to know what the reviewers will be looking for in your contribution.
pre-commit run --allto format old commits.