|
77 | 77 | value |
78 | 78 | (string) semantics determined by the scheme. |
79 | 79 |
|
80 | | -A dependency object MAY contain additional OPTIONAL keys-value pairs, |
| 80 | +A dependency object MAY contain additional OPTIONAL key-value pairs, |
81 | 81 | whose semantics are determined by the scheme. |
82 | 82 |
|
83 | 83 | in jobspec |
@@ -112,6 +112,52 @@ This form SHOULD be translated by the command line tool to the object |
112 | 112 | form above before being shared with other parts of the system. |
113 | 113 |
|
114 | 114 |
|
| 115 | +Simple Dependencies |
| 116 | +------------------- |
| 117 | + |
| 118 | +The following dependency schemes are built-in. |
| 119 | + |
| 120 | +after |
| 121 | +~~~~~ |
| 122 | + |
| 123 | +``value`` SHALL be interpreted as the antecedent jobid, in any valid |
| 124 | +FLUID encoding from RFC 19. |
| 125 | + |
| 126 | +The dependency SHALL be satisfied once the antecedent job enters RUN state. |
| 127 | +If the antecedent job reaches INACTIVE state without entering RUN state, |
| 128 | +a fatal exception SHOULD be raised on the dependent job. |
| 129 | + |
| 130 | + |
| 131 | +afterany |
| 132 | +~~~~~~~~ |
| 133 | + |
| 134 | +``value`` SHALL be interpreted as the antecedent jobid, in any valid |
| 135 | +FLUID encoding from RFC 19. |
| 136 | + |
| 137 | +The dependency SHALL be satisfied once the antecedent job enters INACTIVE |
| 138 | +state, regardless of result. |
| 139 | + |
| 140 | +afterok |
| 141 | +~~~~~~~ |
| 142 | + |
| 143 | +``value`` SHALL be interpreted as the antecedent jobid, in any valid |
| 144 | +FLUID encoding from RFC 19. |
| 145 | + |
| 146 | +The dependency SHALL be satisfied once the antecedent job enters INACTIVE |
| 147 | +state, with a successful result. If the antecedent job does not conclude |
| 148 | +successfully, a fatal exception SHOULD be raised on the dependent job. |
| 149 | + |
| 150 | +afternotok |
| 151 | +~~~~~~~~~~ |
| 152 | + |
| 153 | +``value`` SHALL be interpreted as the antecedent jobid, in any valid |
| 154 | +FLUID encoding from RFC 19. |
| 155 | + |
| 156 | +The dependency SHALL be satisfied once the antecedent job enters INACTIVE |
| 157 | +state, with an unsuccessful result. If the antecedent job concludes |
| 158 | +successfully, a fatal exception SHOULD be raised on the dependent job. |
| 159 | + |
| 160 | + |
115 | 161 | OpenMP-style Dependencies |
116 | 162 | ------------------------- |
117 | 163 |
|
|
0 commit comments