CODEWITHSUNDEEP
pythonhttplocust
obecker
obecker

Reputation: 2377

Locust: got 0 response status_code and None content

I have written a simple load test using Locust (http://locust.io).

Now I noticed that sometimes (using a higher load) the response I get from a post call has a status_code of 0 and a None content. The 0 status code is not automatically recognized as a failure in Locust, so I have to test it manually.

My code fragment is this:

with self.client.get(path, catch_response=True) as response:
    if response.status_code != 200:
        response.failure(path + ": returned " + str(response.status_code))
    elif check not in response.content:
        response.failure(path + ": wrong response, missing '" + check + "'")

Note: check is a variable for a part of the expected response content.

The question is: is this a expected behaviour? Is this a problem of Locust (or Python) or is this a fault in the tested application?

Upvotes: 9

Views: 10399

Answers (3)

Bill--
Bill--

Reputation: 170

Those errors are being swallowed and replaced with a dummy Response:

HttpSession catches any requests.RequestException thrown by Session (caused by connection errors, timeouts or similar), instead returning a dummy Response object with status_code set to 0 and content set to None.

https://docs.locust.io/en/latest/writing-a-locustfile.html#client-attribute-httpsession

It doesn't look like they have any way to not swallow errors.

Upvotes: 1

TechFree
TechFree

Reputation: 2954

My test returned the type of the response was locust.clients.responsecontextmanager but had status_code as 0 and no content, and of course unparseable JSON

It turned out to be the the wrong server URL that I had configured. Check your server logs, if the server indeed received the request and processed it.

Upvotes: 0

Nettok
Nettok

Reputation: 166

From the locust documentation in: http://docs.locust.io/en/latest/writing-a-locustfile.html

Safe mode

The HTTP client is configured to run in safe_mode. What this does is that any request that fails due to a connection error, timeout, or similar will not raise an exception, but rather return an empty dummy Response object. The request will be reported as a failure in Locust’s statistics. The returned dummy Response’s content attribute will be set to None, and it’s status_code will be 0.

It looks like the server can´t handle all the requests you are swarming it with and some of them are timing out.

Upvotes: 12

Related Questions