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
next cd into esmock tests/tests-source-map, upstream location here, then npm install && npm test
see the error
How often does it reproduce? Is there a required condition?
It reproduces every time. Here is a link to a failed CI job that encountered the error, link
screenshot of the error from a win32 virtual machine
What is the expected behavior? Why is that the expected behavior?
When npm test is called, the tests should pass.
Historically, for the last two years or so since that test was added, the test has passed in a matrix of win32 and linux environments running the three or four most recent major versions of node.
What do you see instead?
Additional information
thank you for giving this ticket your attention :)
The text was updated successfully, but these errors were encountered:
Hey, thanks for the detailed report, any chance you could send a repro that do not involve downloading code from the internet (i.e. no repo cloning, no npm install)?
Also, did you try with Node.js 20.x? That would be helpful to figure out the underlying bug.
Version
18.17.0
the error does not occur using 18.16.0
the error does not occur using 20.*
Platform
win32
Subsystem
No response
What steps will reproduce the bug?
npm install
npm install && npm test
How often does it reproduce? Is there a required condition?
It reproduces every time. Here is a link to a failed CI job that encountered the error, link
screenshot of the error from a win32 virtual machine
What is the expected behavior? Why is that the expected behavior?
When
npm test
is called, the tests should pass.Historically, for the last two years or so since that test was added, the test has passed in a matrix of win32 and linux environments running the three or four most recent major versions of node.
What do you see instead?
Additional information
thank you for giving this ticket your attention :)
The text was updated successfully, but these errors were encountered: