Repository navigation
fix(train): stop EvaluationPipelineExecution.wait() on a Stopped execution - #6437
Open
AkshayShah03 wants to merge 1 commit into
Open
AkshayShah03 wants to merge 1 commit into
AkshayShah03 wants to merge 1 commit into
Conversation
…ution wait() returned on the target status and raised on statuses containing 'failed', but did not treat Stopped as terminal. With the default timeout=None, waiting on a stopped evaluation (execution.stop() or a stop from the console) polled forever; with a timeout it eventually raised TimeoutExceededError saying the job is still running. Raise FailedStatusError for Stopped (unless it is the target status), in both the Jupyter and the terminal branches, as trainer_wait already does for Stopped training jobs.
AkshayShah03
requested a deployment
to
manual-approval
October 12, 2026 17:57 — with
GitHub Actions
Waiting
AkshayShah03
requested a deployment
to
manual-approval
October 12, 2026 17:58 — with
GitHub Actions
Waiting
AkshayShah03
requested a deployment
to
manual-approval
October 12, 2026 17:59 — with
GitHub Actions
Waiting
This branch is waiting to be deployed
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.
Issue #, if available: N/A
Description of changes:
EvaluationPipelineExecution.wait()returns on the target status and raises on statuses containing "failed", but doesn't treatStoppedas terminal:timeout=None, waiting on a stopped evaluation polls forever, whether it was stopped withexecution.stop()or from the console;TimeoutExceededErrorsaying the job is still running.This change raises
FailedStatusErrorforStopped, unlessStoppedis the target status. It does this in both the Jupyter and the terminal branches, ascommon_utils/trainer_wait.pyalready does for stopped training jobs. #6423 is the equivalent fix forPipelineExecution.wait()in sagemaker-mlops.Testing:
test_wait_stops_on_stopped_status, wheretime.sleepraises ifwait()keeps polling. It fails before this change, and also checks thatwait(target_status="Stopped")returns.tests/unit/train/evaluate: no new failures. The 2 MTRL handshake tests also fail on master.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.