Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Artillery shows infinite "pending scenarios/requests" while running

See original GitHub issue

I see pending scenarios/requests message keep spinning and never gets completed in my environment(behind the corp proxy with HTTP_PROXY env variable configured accordingly). I am running it with your latest version: artillery version: v1.6.0-9 nodejs version: v8.3.0 npm version: v5.3.0

{
	"config": {
		"target": "http://url.com",
		"phases": [{
				"duration": 1,
				"arrivalRate": 1
			},
			{
				"duration": 1,
				"arrivalRate": 1
			},
			{
				"duration": 1,
				"arrivalRate": 1
			}
		],
		"processor": "./processor.js",
		"payload": [{
			"path": "./data.csv",
			"fields": ["id", "field1", "field2", "field3"]
		}]
	},
	"scenarios": [{
		"beforeRequest": ["preProcessHandler"],
		"afterResponse": ["postProcessHandler"],
		"flow": [{
				"get": {
					"headers": {
						"ID": "{{id}}",
						"Content-Type": "application/json"
					},
					"url": "/action/{{field1}}}"
				}
			},
			{
				"get": {
					"headers": {
						"ID": "{{id}}",
						"Content-Type": "application/json"
					},
					"url": "/action/{{field1}}}/{{field2}}"
				}
			},
			{
				"post": {
					"headers": {
						"ID": "{{id}}",
						"Content-Type": "application/json"
					},
					"url": "/action/{{field1}}",
					"json": {
						"payload": {
							"sample": "{{field3}}"
						},
						"date": "2017-08-01"
					}
				}
			}
		]
	}]
}

And, here is what I am getting as debug logs which shows the same symptom as the previously closed issue #215 :

phases creating a uniform process for arrivalRate +4ms arrivals tickInterval = 1000, duration = 1000 +0ms arrivals this._tickInterval set to 1000000 +1ms arrivals maxArrivals = 1 +0ms Started phase 0, duration: 1s @ 15:45:56(-0400) 2017-09-26 â ¹ runner picking scenario 0 (undefined) weight = 1 +1s perf runScenarioDelta: 6.9 +3ms arrivals maxArrivals reached, stopping +1s phases creating a uniform process for arrivalRate +4ms arrivals tickInterval = 1000, duration = 1000 +2ms arrivals this._tickInterval set to 1000000 +0ms arrivals maxArrivals = 1 +0ms

Started phase 1, duration: 1s @ 15:45:57(-0400) 2017-09-26 processor process start +1s ===keep repeating====================================== / runner Pending requests: 0 +502ms runner Pending scenarios: 3 +2ms / runner Pending requests: 0 +504ms runner Pending scenarios: 3 +4ms / runner Pending requests: 0 +501ms runner Pending scenarios: 3 +2ms / runner Pending requests: 0 +503ms runner Pending scenarios: 3 +3ms \ artillery:runner busyPids: +3s [] | runner Pending requests: 0 +503ms runner Pending scenarios: 3 +2ms | runner Pending requests: 0 +501ms runner Pending scenarios: 3 +2ms | runner Pending requests: 0 +503ms runner Pending scenarios: 3 +2ms | runner Pending requests: 0 +505ms runner Pending scenarios: 3 +4ms

artillery:runner max worker concurrency: {“12896”:3} +2s Report @ 16:02:24(-0400) 2017-09-26 Scenarios launched: 3 Scenarios completed: 0 Requests completed: 0 Concurrent users: 3 RPS sent: NaN Request latency: min: NaN max: NaN median: NaN p95: NaN p99: NaN Scenario duration: min: NaN max: NaN median: NaN p95: NaN p99: NaN

\ runner Pending requests: 0 +502ms runner Pending scenarios: 3 +2ms

artillery:runner busyPids: +623ms [] \ runner Pending requests: 0 +504ms runner Pending scenarios: 3 +3ms \ runner Pending requests: 0 +503ms runner Pending scenarios: 3 +2ms \ runner Pending requests: 0 +503ms runner Pending scenarios: 3 +3ms \ runner Pending requests: 0 +502ms runner Pending scenarios: 3 +2ms

runner Pending requests: 0 +502ms runner Pending scenarios: 3 +2ms / artillery:runner busyPids: +3s []

runner Pending requests: 0 +503ms runner Pending scenarios: 3 +1ms

runner Pending requests: 0 +505ms runner Pending scenarios: 3 +2ms

runner Pending requests: 0 +503ms runner Pending scenarios: 3 +3ms

runner Pending requests: 0 +501ms runner Pending scenarios: 3 +2ms

runner Pending requests: 0 +504ms runner Pending scenarios: 3 +4ms | artillery:runner busyPids: +2s []

runner Pending requests: 0 +502ms runner Pending scenarios: 3 +2ms / runner Pending requests: 0 +502ms runner Pending scenarios: 3 +4ms / runner Pending requests: 0 +505ms runner Pending scenarios: 3 +2ms / runner Pending requests: 0 +504ms runner Pending scenarios: 3 +3ms / runner Pending requests: 0 +503ms runner Pending scenarios: 3 +1ms runner Pending requests: 0 +504ms runner Pending scenarios: 3 +39s \ artillery:runner max worker concurrency: {“12896”:3} +41s Report @ 16:03:11(-0400) 2017-09-26 Scenarios launched: 0 Scenarios completed: 0 Requests completed: 0 Concurrent users: 3 RPS sent: NaN Request latency: min: NaN max: NaN median: NaN p95: NaN p99: NaN Scenario duration: min: NaN max: NaN median: NaN p95: NaN p99: NaN

artillery:runner busyPids: +49ms [] / runner Pending requests: 0 +501ms runner Pending scenarios: 3 +3ms

artillery:runner busyPids: +536ms [] / runner Pending requests: 0 +501ms runner Pending scenarios: 3 +2ms / runner Pending requests: 0 +504ms runner Pending scenarios: 3 +4ms / runner Pending requests: 0 +503ms runner Pending scenarios: 3 +2ms / runner Pending requests: 0 +504ms runner Pending scenarios: 3 +3ms | runner Pending requests: 0 +501ms runner Pending scenarios: 3 +3ms / artillery:runner busyPids: +3s [] | runner Pending requests: 0 +502ms runner Pending scenarios: 3 +2ms | runner Pending requests: 0 +503ms runner Pending scenarios: 3 +3ms | runner Pending requests: 0 +502ms runner Pending scenarios: 3 +2ms | runner Pending requests: 0 +502ms runner Pending scenarios: 3 +2ms | runner Pending requests: 0 +503ms runner Pending scenarios: 3 +2ms artillery:runner busyPids: +3s [] | runner Pending requests: 0 +505ms runner Pending scenarios: 3 +2ms \ runner Pending requests: 0 +501ms runner Pending scenarios: 3 +3ms \ runner Pending requests: 0 +503ms runner Pending scenarios: 3 +2ms \ runner Pending requests: 0 +504ms runner Pending scenarios: 3 +2ms \ runner Pending requests: 0 +503ms runner Pending scenarios: 3 +2ms artillery:runner busyPids: +3s [] \ runner Pending requests: 0 +503ms runner Pending scenarios: 3 +4ms \ runner Pending requests: 0 +504ms runner Pending scenarios: 3 +3ms \ runner Pending requests: 0 +502ms runner Pending scenarios: 3 +2ms ===keep repeating======================================

Issue Analytics

State:
Created 6 years ago
Comments:8 (4 by maintainers)

Top GitHub Comments

1reaction

hassycommented, Sep 27, 2017

OK thanks @anoasis. postProcessorHandle not being invoked is interesting. Have you ruled the HTTP proxy as a possible issue? How long do you leave Artillery running for? Could you try rerunning the script with a short HTTP timeout setting, e.g.:

{
  "config": {
    "http": {
      "timeout": 10
    }
}

0reactions

Alek5andrcommented, Jan 15, 2019

I’m facing the same issue with corporate network. And I cannot figure it out, how to run artillery tests successfully. I have ‘HTTP_PROXY’/‘HTTPS_PROXY’ variables set in OS. Also I tried to set them in test’s ‘config.environments.variables’ section. Still no luck. Only zeros and NaNs. Is corporate proxy too greedy or do I miss something in running artillery?

artillery version: v1.6.0-26 nodejs version: v8.9.4 npm version: v5.6.0

Top Results From Across the Web

Testing HTTP - Artillery.io

If a response to any request takes longer than 10 seconds, Artillery will abort the request and raise an ETIMEDOUT error. To increase...

shoreditch-ops/artillery - Gitter

Possibly relevant: some fumbling with the Node debugger reveals I'm stuck in an infinite loop caused by while(immediate) in Node's timers.js library. I'm ......

Artillery Not Launching Scenarios - ADocLib

Closed Artillery shows infinite pending scenarios/requests while running #379. surveyors of the field artillery target acquisi missile fire and assist when ...

POLICE USE OF DEADLY FORCE - Office of Justice Programs

rules and regulations on how and when deadly force is to be used. Patrick V. Murphy ... knew that, with very rare exceptions,...

Welding Terms and Definitions Dictionary | Red-D-Arc Welder ...

- The travel angle when the electrode is pointing backward. This angle can be used to define the position of welding guns, welding...