-
Notifications
You must be signed in to change notification settings - Fork 93
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
job file: add set -o pipefail for bash jobs #1910
Conversation
(Just need to figure out the best place to document this.) |
The best place to find current known issues is on Github: | ||
\url{https://github.com/cylc/cylc/issues}. | ||
|
||
\subsection{Other Known Issues} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we name this "Notable Known Issues" - that way we can use the section for documenting things like the Family triggering memory overhead and the GraphViz GTK memory leak.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Noted and modified.
Add more info on why the default behaviour of a pipeline in bash is unsafe.
last command. This is unsafe, because if any command in the pipeline fails, the | ||
script will continue nevertheless. | ||
|
||
For safetty, a cylc task job script running in bash will have the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"safety"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
Good, one doc typo. Test pass. |
Close #1783.