Repository navigation
[ci] Validate Attention #6508 with upstream Layer 2 - #6517
Merged
Merged
Conversation
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.
Purpose
Run the existing trusted same-repository Layer 2 checks for #6508, whose fork-origin GPU jobs are skipped.
This is a validation-only duplicate. Keep #6508 as the review and merge target; do not merge this validation PR.
Source
81c2cfb0a6858bcbe5e64cbcae72ec12fe28be04Validation requested
Run the unchanged
CI / Layer 2 / Trusted PR GPUworkflow: batches2 4a 5, with its existing FAST_MODE setting, pinned dependency image, shared GPU lock, and idle-device checks. Batch 5 uses two idle GPUs; the other batches use one.This is the standard core GPU regression. It does not include the separate strict FA3 Attention batch
4f, and is not a replacement for the operator numerical acceptance evidence documented in #6508. Results will be available in this PR's Checks and the workflow artifacts.