Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vitest --retry CLI option is not taken into account in a monorepo setup #4758

Closed
6 tasks done
ddolcimascolo opened this issue Dec 15, 2023 · 3 comments · Fixed by #4774
Closed
6 tasks done

Vitest --retry CLI option is not taken into account in a monorepo setup #4758

ddolcimascolo opened this issue Dec 15, 2023 · 3 comments · Fixed by #4774

Comments

@ddolcimascolo
Copy link

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

@ddolcimascolo
Copy link
Author

I'm willing to help 👍 Let me know if you need more information from me!

Cheers,
David

@yannours
Copy link

Truely a pain, plz send help ❤️

@ddolcimascolo
Copy link
Author

Thx for fixing!

@github-actions github-actions bot locked and limited conversation to collaborators Jan 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants