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

Status reports only shown in terminal, not on the Web interface. #319

Closed
Lordanakun opened this issue Aug 12, 2015 · 2 comments
Closed

Status reports only shown in terminal, not on the Web interface. #319

Lordanakun opened this issue Aug 12, 2015 · 2 comments

Comments

@Lordanakun
Copy link

Hi There,
I really like this tool. It is quite easy to spin up and powerful.

However, I have an issue of the statistic report. When I run a simple test on my Mac with 10 simulated users against my restful api server, everything seems fine except that the Web interface does not provide live status. In fact, the Web interface does not provide any status at all. The status report only shows up when I Ctrl+C to terminate the program in the terminal. Something like this below.

I've searched online for a while, but couldn't find an answer how to make the Web interface alive.

Could you help? Really appreciate your time.

Anakun

[2015-08-12 12:28:00,793] /INFO/locust.main: Shutting down (exit code 0), bye.

Name # reqs # fails Avg Min Max | Median req/s

POST /research/api/v1/auth/signUp 5 5(50.00%) 5320 998 10135 | 6400 0.40

Total 5 5(100.00%) 0.40

Percentage of the requests completed within given times

Name # reqs 50% 66% 75% 80% 90% 95% 98% 99% 100%

POST /research/api/v1/auth/signUp 5 6400 7900 7900 10000 10000 10000 10000 10000 10135

Error report

occurences Error

5 POST /research/api/v1/auth/signUp: '"HTTPError('409 Client Error: Conflict',)"'

@vividhsv
Copy link

You are not seeing any live status because all you requests are failing with '409' from you application under test. In fact, you would see these results on 'Errors' tab of the Web interface.

I guess you are signing up with the same user, hence you are getting 409 Conflict. Correcting this should solve the issue for you

@Lordanakun
Copy link
Author

Hi Vividh,
Thanks for your quick response. Actually, the conflict is part of the test. But, I figured out, and I made a stupid mistake of not refreshing my web interface.

Thanks again!!

Anakun

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

2 participants