-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle diagnostics that fail #327
Comments
I have mixed feelings on this one, as having the workflow hold if a task fails is very useful for debugging. It may be something we want to make dependent of whether debugging logging is enabled. |
jfrost-mo
added a commit
that referenced
this issue
Jan 16, 2025
7 tasks
jfrost-mo
added a commit
that referenced
this issue
Jan 16, 2025
jfrost-mo
added a commit
that referenced
this issue
Jan 16, 2025
jfrost-mo
added a commit
that referenced
this issue
Jan 17, 2025
jfrost-mo
added a commit
that referenced
this issue
Jan 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The entire workflow shouldn't crash if you are just missing a variable used by a single diagnostic. It should exit cleanly, and report the status on the CSET front page.
The text was updated successfully, but these errors were encountered: