...
A node can only have one late attribute. The late attribute only applies to a task. You can define it on a Suite/Family in which case it will be inherited. Any late defined lower down the hierarchy will override the aspect(submitted,active, complete) defined higher up.
- -s submitted: The time node can stay submitted (format [+]hh:mm). submitted is always relative, so + is simple ignored, if present. If the node stays submitted longer than the time specified, the late flag is set
- -a Active : The time of day the node must have become active (format hh:mm). If the node is still queued or submitted, the late flag is set
- -c Complete : The time node must become complete (format {+}hh:mm). If relative, time is taken from the time the node became active, otherwise node must be complete by the time given.
| Code Block | ||
|---|---|---|
| ||
task t1 late -s +00:15 -a 20:00 -c +02:00 |
This is interpreted as: the node can stay submitted for a maximum of 15 minutes, and it must become active by 20:00 and the runtime must not exceed 2 hours.
For the purposes of this tutorial we will add a late attribute for the runtime only.
...