Various vitest test failures since v7.2.10 #555
Description
Describe the bug
We recently updated vite rolldown to v7.2.10 and since then it causes some strange random vitest test failures.
- chore(deps): update dependency vite to v7.2.10 (main) renovatebot/renovate#39891
- https://github.com/renovatebot/renovate/actions/runs/20092423018/job/57642892823
We don't know how to create a minimal reproduction, but the errors are happening regularly on our CI
Reproduction
https://github.com/renovatebot/renovate
Steps to reproduce
Run pnpm install and pnpm vitest
System Info
System:
OS: Linux 6.6 Ubuntu 24.04.3 LTS 24.04.3 LTS (Noble Numbat)
CPU: (32) x64 AMD Ryzen 9 5950X 16-Core Processor
Memory: 27.66 GB / 31.34 GB
Container: Yes
Shell: 5.2.21 - /bin/bash
Binaries:
Node: 24.11.1 - /usr/bin/node
npm: 11.6.2 - /usr/bin/npm
pnpm: 10.24.0 - /usr/bin/pnpm
bun: 1.0.0 - /home/kriese/bin/bun
Deno: 2.0.4 - /home/kriese/.deno/bin/deno
npmPackages:
rolldown-vite: 7.2.10Used Package Manager
pnpm
Logs
Click to expand!
⎯⎯⎯⎯⎯⎯ Failed Suites 1 ⎯⎯⎯⎯⎯⎯⎯
FAIL lib/modules/datasource/crate/index.spec.ts [ lib/modules/datasource/crate/index.spec.ts ]
Error: Obsolete snapshots found when no snapshot update is expected.
· modules/datasource/crate/index > getReleases > clones cloudsmith private registry 1
· modules/datasource/crate/index > getReleases > clones other private registry 1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/7]⎯
⎯⎯⎯⎯⎯⎯⎯ Failed Tests 6 ⎯⎯⎯⎯⎯⎯⎯
FAIL lib/modules/datasource/crate/index.spec.ts > modules/datasource/crate/index > getReleases > clones cloudsmith private registry
AssertionError: expected "clone" to be called at least once
❯ lib/modules/datasource/crate/index.spec.ts:282:25
280| registryUrls: [url],
281| });
282| expect(mockClone).toHaveBeenCalled();
| ^
283| expect(res).toMatchSnapshot();
284| expect(res).not.toBeNull();
Validations
- Follow our Code of Conduct
- Read the Contributing Guidelines.
- Read the docs and the Rolldown-related guide.
- 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.