Repository navigation
test-require-symlink error on Windows 10 #23596
Description
Activity
- changed the title
[-]test-require-symlink[/-][+]test-require-symlink error on Windows 10[/+]on Oct 12, 2018 I had the same error when you have Symlink permissions when running as Administrator. Since admin has symlink permissions. The test seems to skip when you do not have symlink permissions.
The return value required by the
fooModule(foo.js within the tmp dir){ dep1: { bar: { version: 'CORRECT_VERSION' }, dep2: { bar: { version: 'INCORRECT_VERSION' } } }, dep2: { bar: { version: 'INCORRECT_VERSION' } } }
Looks like
dep2,jsrequires the incorrectbar.js- addedwindowsIssues and PRs related to the Windows platform.Issues and PRs related to the Windows platform.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.
on Oct 12, 2018 I've re-ran it again without administrative privileges. One error did come up relating to a parallel HTTP test if I remember correctly. However after running it again after and subsequently, the error is not showing up any more so I am unfortunately unable to report that one.
After a bit of digging, it seems that
module-require-symlink\node_modules\dep1\node_modules\dep2is linked two levels down tomodule-require-symlink\node_modules\dep2. I'm not quite sure how require resolves it's path but sincemodule-require-symlink\node_modules\dep2has nonode_modules\barit resolved tomodule-require-symlink\node_modules\barwhich has the incorrect version. I apologize in advance if I'm just spouting nonsense here.Fix in #23691, thanks for reporting this!
- added a commit that references this issue
on Oct 23, 2018 - added a commit that references this issue
on Oct 24, 2018 - added 2 commits that reference this issue
on Nov 26, 2018 - added 2 commits that reference this issue
on Nov 28, 2018 - added a commit that references this issue
on Nov 29, 2018
This issue occurs when running the tests on Windows with Windows Defender Firewall off while connected to a wireless network. This was executed in a command prompt with administrator privileges on Windows 10 ver 1803 (build 17134.345).