Remove command flag from init pytorch job integ test #351
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
mollyheamazon
temporarily deployed
to
manual-approval
GitHub Actions
Inactive
aviruthen
approved these changes
Dec 12, 2025
Collaborator
aviruthen
left a comment
aviruthen
left a comment
There was a problem hiding this comment.
Approved pending unit/integ tests pass!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
What's changing and why?
Init experience pytorch job integ test has been failure after the HPTO launch. Root cause is that it is using a command flag with previously set command that is no longer supported by the addition of HyperpodElasticAgent installed image. Thus removing this flag so that the job will run successfully.
For how to use container command with HyperpodElasticAgent installed image, see this doc: https://docs.aws.amazon.com/sagemaker/latest/dg/sagemaker-eks-operator-install.html#sagemaker-eks-operator-elastic-agent
Before/After UX
Before:
After:
How was this change tested?
Are unit tests added?
Are integration tests added?
Reviewer Guidelines
One of the following must be true: