Bump apex to c0f56f7e for release/2.11 - #3391
Merged
Merged
Conversation
|
Jenkins build for 958691b6203121fad494ed5e93bb4a662f606837 commit finished as FAILURE |
anatoliylitv
self-requested a review
July 2, 2026 16:03
anatoliylitv
approved these changes
Jul 2, 2026
Update the apex pinned commit in related_commits (ubuntu and centos) from 973a3632 to c0f56f7e on the ROCm apex release/1.11.0 branch. This bump brings in a cherry-pick of ROCm/apex PR #334 (ROCm/apex#334), which fixes non-contiguous inputs in the fused RoPE aiter backend by enforcing last-dim contiguity at the apex/aiter boundary (fixing the "rope_2d_bwd_impl requires all stride_d to be 1" crash on transposed inputs and broadcast/expanded gradients). This is purely a dependency pin update to pull in the fix, not a PyTorch code change. Test Plan: Metadata-only change to the related_commits pin file; no build or test run. Verified the diff updates only the two apex lines. Authored-with: Claude (Anthropic AI assistant).
albmalamd
force-pushed
the
bump_apex_for_2.11
branch
from
July 3, 2026 11:26
958691b to
3d3a7d1
Compare
|
Jenkins build for 3d3a7d1640143e70da0cf6a2f61821a643854d4a commit finished as FAILURE |
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
3 participants
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.
Summary
Updates the apex pinned commit in
related_commitsfor the ROCm apexrelease/1.11.0branch, from973a363235cd056e9da83716aabdd2691df9e70atoc0f56f7eccd343a08a1b0d0be59f1e7e0e9b90b7(both ubuntu and centos lines).This bump brings in a cherry-pick of ROCm/apex PR #334 (ROCm/apex#334), which fixes non-contiguous inputs in the fused RoPE aiter backend by enforcing last-dim contiguity at the apex/aiter boundary (fixing the "rope_2d_bwd_impl requires all stride_d to be 1" crash on transposed inputs and broadcast/expanded gradients). This is purely a dependency pin update to pull in the fix, not a PyTorch code change.
Test plan
related_commitspin file; CI validates apex builds against the new pin.Authored with the assistance of Claude (Anthropic AI assistant).