Surface pipeline job failures to the user - #1734
Merged
BryonLewis merged 1 commit intoJul 1, 2026
Merged
BryonLewis merged 1 commit into
BryonLewis merged 1 commit into
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
When a job process exits non-zero (and was not cancelled), scan its captured output for lines beginning with 'ERROR:' and show them in a dialog. Processes emit a single 'ERROR: <cause>' line to report the real failure reason (e.g. a GPU out-of-memory during SAM3 model load), so the user sees the cause without opening the job log.
BryonLewis
approved these changes
Jul 1, 2026
BryonLewis
left a comment
Copy link
Copy Markdown
Collaborator
There was a problem hiding this comment.
👍
Sorry, something went wrong.
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.
When a pipeline/training job process exits non-zero (and was not cancelled), scan its captured output for lines beginning with ERROR: and show them in a dialog. Processes emit a single ERROR: <cause> line to report the real failure reason (e.g. a GPU out-of-memory during SAM3 model load), so the user sees the cause without opening the job log. General mechanism — any pipeline that prints ERROR: and exits non-zero surfaces it.