bzt 1.14.2 aborts when using the locust as the executor

Products

• BlazeMeter

Issue/Introduction

Bzt 1.14.2 does work when using the locust as the executor. It was working before I upgraded to 1.14.2. Here the output.

13:04:57 INFO: Taurus CLI Tool v1.14.2
13:04:57 INFO: Starting with configs: ['locust.yml']
13:04:57 INFO: Configuring...
13:04:57 INFO: Artifacts dir: /Users/xxxxx/Locust/taurus/2020-04-20_13-04-57.666227
13:04:57 INFO: Preparing...
13:04:59 INFO: Starting...
13:04:59 INFO: Waiting for results...
13:04:59 INFO: Waiting for finish...
13:05:00 WARNING: Locust exited with non-zero code: 1
13:05:00 WARNING: Please wait for graceful shutdown...
13:05:00 INFO: Shutting down...
13:05:00 INFO: Post-processing...
13:05:00 INFO: Test duration: 0:00:01
13:05:00 ERROR: Child Process Error: Empty results, most likely example (LocustIOExecutor) failed. Actual reason for this can be found in logs under /Users/xxxxx/Locust/taurus/2020-04-20_13-04-57.666227
13:05:00 ERROR: Locust STDERR:
Traceback (most recent call last):
File "/usr/local/Cellar/bzt/1.14.2/libexec/lib/python3.7/site-packages/bzt/resources/locustio-taurus-wrapper.py", line 9, in
from locust import main, events, runners
ModuleNotFoundError: No module named 'locust'
13:05:00 INFO: Artifacts dir: /Users/xxxxx/Locust/taurus/2020-04-20_13-04-57.666227
13:05:00 WARNING: Done performing with code: 1

Cause

We are using Locust version 0.14.5.

Environment

Release :

Component : PACKAGE CA BLAZEMETER

Resolution

We currently do not support Locust 0.14.5. We only support Locust 0.13-0.13.5, per the Taurus documentation.
This is the reason for the error you are seeing. You will need to use a supported release of Locust.

https://gettaurus.org/docs/Locust/