@@ -305,16 +305,26 @@ class Runnable(proto.Message):
305
305
to understand the logs. If not provided the
306
306
index of the runnable will be used for outputs.
307
307
ignore_exit_status (bool):
308
- Normally, a non-zero exit status causes the
309
- Task to fail. This flag allows execution of
310
- other Runnables to continue instead.
308
+ Normally, a runnable that returns a non-zero exit status
309
+ fails and causes the task to fail. However, you can set this
310
+ field to ``true`` to allow the task to continue executing
311
+ its other runnables even if this runnable fails.
311
312
background (bool):
312
- This flag allows a Runnable to continue
313
- running in the background while the Task
314
- executes subsequent Runnables. This is useful to
315
- provide services to other Runnables (or to
316
- provide debugging support tools like SSH
317
- servers).
313
+ Normally, a runnable that doesn't exit causes its task to
314
+ fail. However, you can set this field to ``true`` to
315
+ configure a background runnable. Background runnables are
316
+ allowed continue running in the background while the task
317
+ executes subsequent runnables. For example, background
318
+ runnables are useful for providing services to other
319
+ runnables or providing debugging-support tools like SSH
320
+ servers.
321
+
322
+ Specifically, background runnables are killed automatically
323
+ (if they have not already exited) a short time after all
324
+ foreground runnables have completed. Even though this is
325
+ likely to result in a non-zero exit status for the
326
+ background runnable, these automatic kills are not treated
327
+ as task failures.
318
328
always_run (bool):
319
329
By default, after a Runnable fails, no further Runnable are
320
330
executed. This flag indicates that this Runnable must be run
@@ -607,16 +617,14 @@ class TaskSpec(proto.Message):
607
617
scripts, executable containers, and/or barriers) for each
608
618
task in this task group to run. Each task runs this list of
609
619
runnables in order. For a task to succeed, all of its script
610
- and container runnables each must either exit with a zero
611
- status or enable the ``ignore_exit_status`` subfield and
612
- exit with any status.
613
-
614
- Background runnables are killed automatically (if they have
615
- not already exited) a short time after all foreground
616
- runnables have completed. Even though this is likely to
617
- result in a non-zero exit status for the background
618
- runnable, these automatic kills are not treated as Task
619
- failures.
620
+ and container runnables each must meet at least one of the
621
+ following conditions:
622
+
623
+ - The runnable exited with a zero status.
624
+ - The runnable didn't finish, but you enabled its
625
+ ``background`` subfield.
626
+ - The runnable exited with a non-zero status, but you
627
+ enabled its ``ignore_exit_status`` subfield.
620
628
compute_resource (google.cloud.batch_v1alpha.types.ComputeResource):
621
629
ComputeResource requirements.
622
630
max_run_duration (google.protobuf.duration_pb2.Duration):
0 commit comments