Skip to content

Odd message when running watch mode with no match test filter #6949

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

Closed
6 tasks done
hi-ogawa opened this issue Nov 22, 2024 · 2 comments · Fixed by #7246
Closed
6 tasks done

Odd message when running watch mode with no match test filter #6949

hi-ogawa opened this issue Nov 22, 2024 · 2 comments · Fixed by #7246
Labels
p3-minor-bug An edge case that only affects very specific usage (priority)

Comments

@hi-ogawa
Copy link
Contributor

Describe the bug

It says "exiting" but it doesn't in watch mode. Also new summary reporter's "Duration" keeps increasing 😄

image

Reproduction

https://stackblitz.com/edit/vitest-dev-vitest-zd2zyx?file=package.json

System Info

System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    vitest: 2.2.0-beta.2 => 2.2.0-beta.2

Used Package Manager

npm

Validations

@hi-ogawa hi-ogawa added pending triage p3-minor-bug An edge case that only affects very specific usage (priority) and removed pending triage labels Nov 22, 2024
@AriPerkkio
Copy link
Member

Is this only on latest 2.2.0 beta releases?

@AriPerkkio
Copy link
Member

AriPerkkio commented Nov 26, 2024

Looks like this has been broken since 2.0.0-beta.13. The 2.0.0-beta.12 and 1.6.0 work fine.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
p3-minor-bug An edge case that only affects very specific usage (priority)
Projects
None yet
2 participants