Please take a not note of ECFLOW-1436, as the way certain relative triggers are interpreted has changed.
Code Block |
---|
title | ecflow 4.11.0 or less, these are now errors in 4.12.0 |
---|
| ...
family f1
task t1
trigger f1 == aborted
task t2
trigger ./f1 == aborted |
|
Code Block |
---|
title | corrected triggers in ecflow 4.12.0 |
---|
| ...
family f1
task t1
trigger ../f1 == aborted
task t2
trigger ../f1 == aborted |
|
---|
You can detect these triggers in ecflow 4.12.0. If you have generated your suite definitions in python, then you can use: Code Block |
---|
module load ecflow/4.12.0 # the 4.12.0 release has the new check |
Code Block |
---|
language | py |
---|
title | Check Triggers |
---|
| # build your suite defeinitions
def = ...
print defs.check() # this will check the trigger expressions |
Alternatively you can use: Code Block |
---|
language | bash |
---|
title | Check triggers on the comand line |
---|
| ecflow_client --get > tmp.def
module swap ecflow/4.12.0
ecflow_client --load tmp.def check_only |
If you have already converted to using ecflow 4.12.0 server, you can check your trigger expressions using: Code Block |
---|
title | Check triggers in ecflow 4.12.0 server |
---|
| module load ecflow/4.12.0
ecflow_client --check=_all_ |
|