Timeout configure when test duration too long

[ke yi]

Hi, folks. 

Is there any option to set timeout threshold when execute bzt command, I expect test will be forcibly log and closed/move forward after such threshold exceed, like 15s? In my local test, long duration sometimes happened and test process will keep looping forever.

my configure json:

{

"execution": [

{

"concurrency": 100,

"ramp-up": "30s",

"hold-for": "30s",

"scenario": "max1000"

}

],

"scenarios": {

"max1000": {

"requests": [

{

"url": "http://www.bing.com",

"method": "GET",

"body": {},

"headers": {}

}

]

}

},

"reporting": [

{

"module": "final-stats",

"summary": true,

"percentiles": true,

"summary-labels": true,

"test-duration": true,

"dump-xml": "/tmp/artifacts/results.xml"

}

]

}

log as follows:

2021-01-26T14:54:20.468+08:00
06:54:20 INFO: Changed data analysis delay to 25s

2021-01-26T14:54:20.482+08:00
06:54:20 INFO: Current: 100 vu 20 succ 0 fail 3.462 avg rt / Cumulative: 2.738 avg rt, 0% failures

2021-01-26T14:54:22.459+08:00
06:54:22 INFO: Changed data analysis delay to 27s

2021-01-26T14:54:22.479+08:00
06:54:22 INFO: Current: 100 vu 21 succ 0 fail 2.910 avg rt / Cumulative: 2.748 avg rt, 0% failures

2021-01-26T14:54:26.450+08:00
06:54:26 INFO: Changed data analysis delay to 32s

2021-01-26T14:54:26.474+08:00
06:54:26 INFO: Current: 100 vu 31 succ 0 fail 5.451 avg rt / Cumulative: 2.912 avg rt, 0% failures

2021-01-26T14:54:32.750+08:00
06:54:32 INFO: Changed data analysis delay to 38s

2021-01-26T14:54:32.850+08:00
06:54:32 INFO: Current: 100 vu 36 succ 0 fail 4.336 avg rt / Cumulative: 3.019 avg rt, 0% failures

[grey....@gmail.com]

Hello.
Feel free to find 'timeout' on our site. (e.g. https://gettaurus.org/docs/JMeter/#Global-Settings)

You can configure it with something like that:

...

"scenarios": {

"max1000": {

"timeout": "15s",

"requests": [

...

---

Taras

[ke yi]

thanks, appreciate your quick response.

[Brice Burgess]

I am not seeing a global timeout documented in https://gettaurus.org/docs/JMeter/#Global-Settings

It is showing a timeout for requests, e.g. 500ms. But it is not showing/documenting a 'global' timeout; e.g. if this test/scenario runs for more than 1h, fail/terminate it.

you example shows timeout under scenarios block, while the linked documentation shows timeout under the scenarions.requests block.

Also is this timeout setting limited to jmeter executor?

Thanks!

[grey....@gmail.com]

Hi Brice.

1. It isn't easy question due to a lot of different testing tools tools, you know (e.g. some of them don't support any timeouts). 

At least for jmeter and selenium afaik both of timeouts (request and scenario level) are supported. 

2. We have no 'global' timeout, let's recognize 'scenario timeout' as 'global'

3. What about your hanging case, it's famous jmeter problem and we're thinking from time to time whether we should fix it on our side or not. 

The cause of the problem is having no timeout (in jmeter) by default. 

It's annoying, scenario timeout as workaround should help you. Please note: it doesn't work with existing jmx scripts.

---

Taras