test(checkpoint): respect effective pinning capability - #86
Draft
aws-mengchiy wants to merge 1 commit into
Draft
Conversation
(cherry picked from commit 3dbc406)
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.
Summary
Literal cherry-pick of
3dbc406f015ontorelease/pt_213.StateDictStagerdisables requested pinning when CUDA is unavailable, but the device-generalized test asserted the requestedpin_memoryflag. Assert againststager.pin_memory, the effective capability-gated value, while retaining all four pin/share configurations and shared-memory coverage.Validation
python -m py_compile test/distributed/checkpoint/test_state_dict_stager.py2.12.1+cpu: the exact test passes with--runxfail(1 passed, 4 subtests passed).