Describe the bug
In a monorepo setup, running Vitest at the root as documented in https://vitest.dev/guide/workspace.html does not handle the --retry CLI option used to retry failing tests. The option works perfectly fine in each individual projects.
Reproduction
Minimal reproduction repository: https://github.com/ddolcimascolo/vitest-retry-monorepo
System Info
System:
OS: Linux 6.2 Linux Mint 21.2 (Victoria)
CPU: (16) x64 11th Gen Intel(R) Core(TM) i7-11850H @ 2.50GHz
Memory: 1.48 GB / 15.34 GB
Container: Yes
Shell: 5.1.16 - /bin/bash
Binaries:
Node: 20.9.0 - ~/.nvm/versions/node/v20.9.0/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v20.9.0/bin/yarn
npm: 10.1.0 - ~/.nvm/versions/node/v20.9.0/bin/npm
Browsers:
Chrome: 120.0.6099.109
npmPackages:
vite: 5.0.10 => 5.0.10
vitest: 1.0.4 => 1.0.4
Used Package Manager
npm
Validations
Describe the bug
In a monorepo setup, running Vitest at the root as documented in https://vitest.dev/guide/workspace.html does not handle the
--retryCLI option used to retry failing tests. The option works perfectly fine in each individual projects.Reproduction
Minimal reproduction repository: https://github.com/ddolcimascolo/vitest-retry-monorepo
System Info
System: OS: Linux 6.2 Linux Mint 21.2 (Victoria) CPU: (16) x64 11th Gen Intel(R) Core(TM) i7-11850H @ 2.50GHz Memory: 1.48 GB / 15.34 GB Container: Yes Shell: 5.1.16 - /bin/bash Binaries: Node: 20.9.0 - ~/.nvm/versions/node/v20.9.0/bin/node Yarn: 1.22.19 - ~/.nvm/versions/node/v20.9.0/bin/yarn npm: 10.1.0 - ~/.nvm/versions/node/v20.9.0/bin/npm Browsers: Chrome: 120.0.6099.109 npmPackages: vite: 5.0.10 => 5.0.10 vitest: 1.0.4 => 1.0.4Used Package Manager
npm
Validations