Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

self interrupt for inline nested TaskSets? #631

Closed
daluu opened this issue Jul 23, 2017 · 2 comments
Closed

self interrupt for inline nested TaskSets? #631

daluu opened this issue Jul 23, 2017 · 2 comments

Comments

@daluu
Copy link

daluu commented Jul 23, 2017

It wasn't clear in the documentation: http://docs.locust.io/en/latest/writing-a-locustfile.html#tasksets-can-be-nested, perhaps some additional elaboration in the docs would be nice.

If using inline nested task sets, would the nested task set also need to include a stop function that calls self.interrupt()? Or that's more implied when nested inline? I assume I have to explicitly include.

@johnblakey
Copy link

I went ahead and explicitly included the self.interrupt() with my nested tasks. I believe the nested tasks are working correctly, but I haven't verified the same behavior without the self.interrupt().

@heyman
Copy link
Member

heyman commented Oct 27, 2017

Yeah, interrupt() needs to be called, or else the execution will continue forever within that TaskSet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants