Skip to content

Change index VUs form 1 to 0 #6268

Description

@Pej0815

Brief summary

Index of first VU moved from 1 to 0.
Which leads to 2 Problems:

  1. Numbers of VU is 1 larger than the one given in the executers given in the options part
  2. If source of test has to be changed, if it uses variable __VU for controlling tasks or as index of arrays

k6 version

2.1.0

OS

Windows 11, Linux

Docker version and image (if applicable)

No response

Steps to reproduce the problem

use test.js with

export const options = {

scenarios: {
contacts: {
executor: 'ramping-vus',
startVUs: 1,
stages: [
{ duration: '1m', target: 9 },
{ duration: '1m', target: 9 },
],
gracefulRampDown: '30s',
},
}

and log the __VU in the default function

Expected behaviour

first __VU shall be 1 again or executers shall be fixed to new start of counting

Actual behaviour

__VU starts at 0

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions