ci: force newest LLVM/compiler-rt on macos-latest (sanitizer-hang test) - #15
Open
fornwall wants to merge 2 commits into
Open
ci: force newest LLVM/compiler-rt on macos-latest (sanitizer-hang test)#15fornwall wants to merge 2 commits into
fornwall wants to merge 2 commits into
Conversation
This is an experiment PR testing whether a newer conda-forge LLVM / compiler-rt runtime resolves the intermittent macos-latest ctest hang in the drivers-test-conda job while keeping ASan+UBSan ON. The compiler is not pinned: ci/conda_env_cpp.txt just lists `compilers`, which conda-forge resolves to its global-default clang (older than the newest). The sanitizer runtime (compiler-rt) comes from conda-forge's LLVM, not Apple Xcode. This adds a step that forces the newest LLVM stack (clang/clangxx/compiler-rt/llvm-tools >= 22) into the active env so we can see if a newer sanitizer runtime fixes the hang. The change is scoped to macos-latest only (via `if: matrix.os == 'macos-latest'`), so the working ubuntu-latest and macos-15-intel jobs are unaffected. Sanitizers remain enabled -- the whole point is to test the newer toolchain with ASan+UBSan still ON. Sibling PRs #12/#13/#14 test disabling the sanitizers instead. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MGR3kc3rh5sS7a3Yn3wP7p
Avoids a second mamba install re-solving (and possibly diverging from or silently no-op'ing over) the env the first solve pinned to clang 19.
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
1 participant
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.
This is an experiment PR testing whether a newer conda-forge LLVM / compiler-rt runtime resolves the intermittent macos-latest ctest hang in the
drivers-test-condajob while keeping ASan+UBSan ON.The compiler is not pinned:
ci/conda_env_cpp.txtjust listscompilers, which conda-forge resolves to its global-default clang (currently 19, older than the newest). That default is set by conda-forge's global pin inconda-forge-pinning-feedstock'sconda_build_config.yaml— look upclang_compiler_version/clangxx_compiler_versionto see the current default. The sanitizer runtime (compiler-rt) comes from conda-forge's LLVM, not Apple Xcode. This PR adds a step that forces the newest LLVM stack (clang/clangxx/compiler-rt/llvm-tools>= 22) into the active env so we can see if a newer sanitizer runtime fixes the hang.The change is scoped to macos-latest only (via
if: matrix.os == 'macos-latest'), so the working ubuntu-latest and macos-15-intel jobs are unaffected. Sanitizers remain enabled -- the whole point is to test the newer toolchain with ASan+UBSan still ON.Sibling PRs #12/#13/#14 test disabling the sanitizers instead.
🤖 Generated with Claude Code
https://claude.ai/code/session_01MGR3kc3rh5sS7a3Yn3wP7p