stop/interrupt weighting/logic for nested tasks that execute a single task

[daluu]

It's not clear from the documentation http://docs.locust.io/en/latest/writing-a-locustfile.html#tasksets-can-be-nested, maybe some elaboration would help, or another example.

Say if I wanted to have:

Main task

• sub task 1
  • subtask 1 function
    • sub sub task A
      • sub sub task A function (when done, we want to return to subtask 1 and from there return to main task)

• sub task 2
  • subtask 2 function
    ...

In such a setup, would sub task 1 need to include a stop function in addition to the "subtask 1 function" so that it exits back to main task? And similarly the sub sub task A needs a stop function to return to subtask 1? If so, would stop() be weighted 1 and the other task function be also weighted 1, or should task be weight 2 and stop() be weight 1 so that we always execute the task before execute stop?

Or just call self.interrupt() at the end of sub task 1, sub sub task A? So no need for separate stop task method with weighting? Or no need for interrupt when have only single task subtasks?

[cyberw]

Closing this due to lack of activity. I hope you solved your issue, otherwise try slack!

[daluu]

Thanks for the suggestion. Just noting down the response received on slack in case others have a similar question as I:

You have to call the interrupt() somewhere for the Locust to stop executing within the current TaskSet and return to the parent. (edited)