process.env.VITEST_WORKER_ID can be larger than maxThreads

Describe the bug

We are migrating our Jest test code over to vitest. We use process.env.JEST_WORKER_ID to allocate a separate database for each worker/thread. With Jest that JEST_WORKER_ID is always between 1 and the maximum number of workers.

In vitest process.env.VITEST_WORKER_ID seems to have another meaning and is ever increasing. The documentation states that VITEST_WORKER_ID can be used to distinguish between threads. In my opinion this is not what it actually does.

Reproduction

Run any test-sutie and see that VITEST_WORKER_ID increases. In watch-mode it increases with each run.

System Info

System:
    OS: macOS 12.4
    CPU: (10) arm64 Apple M1 Max
    Memory: 1.36 GB / 64.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
    Yarn: 3.1.0 - ~/.nvm/versions/node/v16.13.1/bin/yarn
    npm: 8.10.0 - ~/.nvm/versions/node/v16.13.1/bin/npm
  Browsers:
    Chrome: 102.0.5005.115
    Firefox: 100.0.2
    Safari: 15.5
  npmPackages:
    vitest: 0.14.2 => 0.14.2

Used Package Manager

yarn

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn’t already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[flunderpero]

Yes, it is!

[flunderpero]

Wow, that was quick! It’s ok for me that it may change. Thank you!