Locust.io test never stops when using taurus

77 views
Skip to first unread message

Marvin Dean

unread,
Jun 15, 2016, 12:35:34 PM6/15/16
to codename-taurus
Running a locust.io test in Taurus will never quit on it's own making it impossible to run in jenkins builds.

I always have to abort the build to get it to stop even if I set and override with the duration.  NOTE:  All my requests below are failing but that is unrelated.  Happens also if they are passing 100% too.

09:28:56 INFO: Screen 140x35 chars: ┌──── 1 10 users, 2 ~0 active ────┐┌───────────────── Latest Interval Stats at 09:28:52 ────────────────┐┌─┬─┐ │ │.................................││ Average Times: Percentiles: Response Codes: │ │ │ │.................................││ Full: 0.001 0.0%: 0.001 500: 100.00% (7)│ │ ┌───┐ ┬ ┬ ┬──┐ ┬ ┬ ┌───┐ │ │.................................││ Connect: 0.000 50.0%: 0.001 All: 100.00% (7)│ │ ┌───┤ │ │ │ │ │ └───┐ │ │.................................││ Latency: 0.000 90.0%: 0.002 │ ┴ └───┴ └───┴ ┴ └───┴ └───┘ │ │.................................││ ~Receive: 0.001 95.0%: 0.002 │ | v1.6.2 by BlazeMeter.com | │ │.................................││ 99.0%: 0.002 │ │ │.................................││ 99.9%: 0.002 │Script: nodetest.py │ │.................................││ 100.0%: 0.002 │ 100 % │ │.................................││ │Elapsed: 00:01:44 Overtime:│ │.................................││ │ 00:00:14│ └─────────────────────────────────┘└────────────────────────────────────────────────────────────────────┘ │ ┌─────── 1 7 hits, 2 7 fail ──────┐┌────────────────── Cumulative Stats after 00:01:44 ─────────────────┐ local │ │ o o ││ Average Times: Percentiles: Response Codes: │ cpu: 9.000 │ │ o o o o o ││ Full: 0.001 0.0%: 0.001 500: 100.00% (771)│ mem: 25.800 │ │o o o oo oo o o oo o ││ Connect: 0.000 50.0%: 0.001 All: 100.00% (771)│ bytes-sent: 1099.621 │ │o o o o o ooooooooo o oooooo ││ Latency: 0.000 90.0%: 0.002 │ bytes-recv: 1159.600 │ │ooo ooooo o ooooooooo ooooooooo o││ ~Receive: 0.001 95.0%: 0.002 │ disk-read: 0.000 │ │ooooooooooooooooooooooooooooooooo││ 99.0%: 0.003 │ disk-write: 0.000 │ │ooooooooooooooooooooooooooooooooo││ 99.9%: 0.005 │ disk-space: 13.900 │ │ooooooooooooooooooooooooooooooooo││ 100.0%: 0.005 │ engine-loop: 0.160 │ │ooooooooooooooooooooooooooooooooo││ │ │ │ooooooooooooooooooooooooooooooooo││ │ │ └─────────────────────────────────┘│ │───────────────────────────────────│ ┌─────────────────────────────────┐│ Labels Hits Failures Avg Time │ │ │ . . ││All Quotes GET 205 100.00% 0.001 │ │ │ .. . ││Delete Quote DELETE 78 100.00% 0.001 │ │ │ .. . . ││New Quote POST 224 100.00% 0.001 │ │ │.................................││/quote/:id GET 132 100.00% 0.001 │ │ │.................................││Update Quote PUT 69 100.00% 0.001 │ │ │.................................││Random Quote GET 63 100.00% 0.001 │ │ │.................................││ │ │ │.................................││ Errors: │ │ │.................................││1 of: HTTPConnectionPool(host='localhost', port=3412): Max retries e│ │ └─────────────────────────────────┘└────────────────────────────────────────────────────────────────────┘ │ Build was aborted Aborted by anonymous Recording plot data Saving plot series data from: /var/lib/jenkins/jobs/TaurusPerformanceTest/workspace/.idea/.name Not creating point with null values: y=null label= url= [BFA] Scanning build for known causes... [BFA] No failure causes found [BFA] Done. 0s Finished: ABORTED

upcd...@gmail.com

unread,
Jun 15, 2016, 12:39:29 PM6/15/16
to codename-taurus
Hi.

Unfortunately, locust doesn't support 'hold-for' or similar options to limit test execution time. You can use 'iterations' option to specify limit the number of requests.


  Dmitri

Marvin Dean

unread,
Jun 15, 2016, 1:19:38 PM6/15/16
to codename-taurus, upcd...@gmail.com
Thanks,  Sorry I somehow missed that in the documentation.  Iterations is a good workaround.
Reply all
Reply to author
Forward
0 new messages