I just noticed that CYLC_TASK_TRY_NUMBER does not update after the number of executions limit has been reached. Reading the docs, it sounds like this number only increments with an automatic retry. This seems like an odd feature to me. I expected that it would increment every time the task was run. If it passed and I ran it, I would expect the try number to increase by one. If it failed and I manually run it, I expected the try number to increment by one.
I guess my question is - is the current implementation the behaviour other people expect, or should it be like how I describe it above?
With a suite.rc of
[scheduling] [[dependencies]] graph = "hello" [runtime] [[hello]] script = false [[[job]]] execution retry delays = 2*PT2S
If I force the task
hello to run after it has tried three times, the CYLC_TASK_TRY_NUMBER never iterates above 3.
$ grep CYLC_TASK_TRY_NUMBER 0?/job 01/job: export CYLC_TASK_TRY_NUMBER=1 02/job: export CYLC_TASK_TRY_NUMBER=2 03/job: export CYLC_TASK_TRY_NUMBER=3 04/job: export CYLC_TASK_TRY_NUMBER=3 05/job: export CYLC_TASK_TRY_NUMBER=3
Please note, I haven’t checked any version of Cylc later than 7.8.4 as that is what is installed on the VM I’m using.