No test suite found on windows for v0.28.5+

[xsjcTony]

Describe the bug

Hey, I'm running vitest via npm scripts on Windows, which results in no test suite found for all test files.

It might be related to #2020 since it's working for me if I run the command in the docker environment which is WSL (I guess, not sure). But I still want it to be runnable locally.

Downgrading to v0.28.4 solves the issue, which means the problem only exists for version v0.28.5 and later (I suspect some changes caused this in v0.28.5 release)

Since it's only happening on my local, so I don't think it's reproducible, but I would highly appreciate it if someone can inspect it.

Reproduction

Unfortunately no reproduction available :( reason described above.

System Info

System:
    OS: Windows 10 10.0.22000
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
    Memory: 16.28 GB / 31.69 GB
  Binaries:
    Node: 16.18.0 - C:\Program Files\nodejs\node.EXE
    npm: 8.19.2 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22000.120.0), Chromium (110.0.1587.56)
    Internet Explorer: 11.0.22000.120
  npmPackages:
    @vitejs/plugin-react-swc: ^3.2.0 => 3.2.0
    @vitest/coverage-c8: ^0.29.1 => 0.29.1
    @vitest/coverage-istanbul: ^0.29.1 => 0.29.1
    @vitest/ui: ^0.29.1 => 0.29.1
    vite: ^4.1.4 => 4.1.4
    vitest: ^0.29.1 => 0.29.1

Used Package Manager

npm

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.

[github-actions]

Hello @xsjcTony. Please provide a minimal reproduction using a GitHub repository or StackBlitz. Issues marked with need reproduction will be closed if they have no activity within 3 days.

[sheremet-va]

You can provide any reproduction, you don't have to use stackblitz

[xsjcTony]

@sheremet-va Hey, I'm sorry that it somehow works again.. even in my original case. I'm so confused😢.

I'll close the issue anyway, but in case it happens again I'll re-open the issue and attach a reproduction. Thanks for that.

[xsjcTony]

@sheremet-va Hi, I've encountered the problem again, and here's the reproduction:

https://github.com/xsjcTony/vitest-bug-repord

Please clone and run

npm install
npm run test:unit

It will result in

[xsjcTony]

Just FYI, Issue still exists in v0.29.2

[SergioJuniorCE]

Any updates?