You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I'm experiencing something similar to what #415 showed: whenever I run the test runner, the console starts spitting errors about jest-haste-map with references to folders that are outside of the repo.
$ test-storybook
jest-haste-map: duplicate manual mock found: <some function name>
The following files share their name; please delete one of them:
* <rootDir>/<path to some file that is not on the repo>
* <rootDir>/<path to some file that is not on the repo> # same file, but from different worktrees
# ... or either ...
jest-haste-map: Haste module naming collision: <some module name>
The following files share their name; please adjust your hasteImpl:
* <rootDir>/<path to some file that is not on the repo>
* <rootDir>/<path to some file that is not on the repo> # same file, but from different worktrees
# same thing many many times with other files and many not from the repo I intended the tests to run
I work in a team with other devs and no one else experiences this. After reading the last comment on the aforementioned issue I realized that tmy setup is slightly different than the rest because I use worktrees, and the problem is likely that the test runner is not finding the expected content inside the .git folder, as for worktrees this is not a directory but a reference to the main worktree's one.
To Reproduce
Steps to reproduce the behavior:
Have repo with test runner configured
Make worktree of the repo. Will need a second branch, git won't let you check out the same branch twice across worktrees
Describe the bug
I'm experiencing something similar to what #415 showed: whenever I run the test runner, the console starts spitting errors about
jest-haste-map
with references to folders that are outside of the repo.I work in a team with other devs and no one else experiences this. After reading the last comment on the aforementioned issue I realized that tmy setup is slightly different than the rest because I use worktrees, and the problem is likely that the test runner is not finding the expected content inside the
.git
folder, as for worktrees this is not a directory but a reference to the main worktree's one.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Test runs.
System
Additional context
-s
seems to fix the issue.The text was updated successfully, but these errors were encountered: