fix(ci): reuse stable Metal build environment - #1738
Merged
Conversation
Signed-off-by: AlpinDale <alpindale@gmail.com>
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.
Metal nightlies build multiple commits per job. Isolated uv builds rotate temporary environments, while generated CMake targets retain absolute Torch library paths. Create one Python 3.13 build environment per job and use uv build --no-build-isolation for every commit.\n\nValidation:\n- repository hooks, actionlint hook, bash -n, ShellCheck, and diff checks pass\n- two consecutive complete Metal wheels built in one environment on Apple Silicon\n- both wheels installed and loaded native Metal paged-attention kernels\n- second native build reported 'ninja: no work to do', confirming incremental reuse