Vitest 3.0.6 and 3.0.7 hangs up if an entry in exclude option starts with /

[exoego]

Describe the bug

My vitest.config.ts had /__fixtures__/ in exclude option.
https://github.com/exoego/esbuild-bundle-analyzer/pull/124/files#diff-2ee894bf23aa44ff4ce12a3da8af19ab20180474ebf2176dbe5f2eea3f96dc92L15

It worked until Vitest 3.0.5.
But on Vitest 3.0.6 and 3.0.7, test process hangs up forever.

This hang-up is also observed in GitHub Action and job gets canceled after 5 minutes.

After some tries, it appears that an entry in exclude option staring with / causes this issue.

    exclude: [
      // These work finely
      // '**/__fixtures__/**',
      // '__fixtures__/**',

      // But this doesn't work: it hangs up
      '/__fixtures__/**',
    ]

Reproduction

1. git clone https://github.com/exoego/vitest-hung-repro
2. cd vitest-hung-repro
3. npm i
4. npm run test

System Info

System:
    OS: macOS 14.7.3
    CPU: (10) arm64 Apple M1 Pro
    Memory: 242.66 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.4.0 - ~/.asdf/installs/nodejs/22.4.0/bin/node
    npm: 10.8.1 - ~/.asdf/installs/nodejs/22.4.0/bin/npm
  Browsers:
    Chrome: 133.0.6943.142
    Safari: 18.2
  npmPackages:
    vitest: ^3.0.4 => 3.0.7

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.

[AriPerkkio]

Maybe side-effect of #7504 🤔

[hi-ogawa]

It looks like a tinyglobby issue. I reported it there SuperchupuDev/tinyglobby#99.

[hi-ogawa]

@exoego Btw, I don't think /__fixtures__/** was functioning as filter even on previous versions. Can you confirm?

[exoego]

Correct, /__fixtures__/ seems not working as file patterns, as far as I tested. My bad.
I expected it is treated as relative path from the repo root, but it is not.

My expectation as user is:

1. Don't hang up. Because it is not easy to understand what was a cause without error message.
2. (good to have) Warning if patterns are meaningless or broken

[yanai101]

Same here!!!
V 3.0.5 work fine but 3.0.6/7 stacking the terminal (I'm with - m3 mac pro)