In reply to chr_sue:
Your example kills already finished sequence.
Yeah, that’s not the important thing here.
I understand what you were trying to say.
I can kill the sequence in the test rather than in the sequence.
I can also achieve the same by calling stop_sequences() of the sequencer.
In both cases, the state of the sequence successfully moves to STOPPED.
And can be executed again at the second call.
However, in my case, the sequence itself is the one who knows whether to kill it or not.
So I actually would like to kill the sequence “in the sequence”.
Also, I do not want to add dependency on the test and make things more complex.
And, whatever the reason may be, I want to know why the sequence state does not move to STOPPED when kill() is called in the sequence.