Closed phracek closed 2 years ago
I can't reproduce this failure. Maybe you have some stale dependencies?
Some more information:
> pino@7.5.1 test /opt/app-root/src
> npm run lint && tap test/*test.js test/*/*test.js && jest test/jest && npm run test-types
> pino@7.5.1 lint /opt/app-root/src
> eslint .
TAP version 13
ok 1 - test/basic.test.js # time=1239.487ms {
# Subtest: pino version is exposed on export
ok 1 - should be equal
1..1
Please provide a minimal reproduction. We do not see this error in our CI.
On Fedora 34, clone this repository and call commands:
pino@7.5.1 test /opt/app-root/src npm run lint && tap test/test.js test//*test.js && jest test/jest && npm run test-types
pino@7.5.1 lint /opt/app-root/src eslint .
or only npm test
in the cloned directory
I do not have a Fedora environment available or the time to create one unfortunately :/.
This looks like to be specific to Jest and Fedora... something that is a very complex setup to preproduce and maintain support for.
If you want I can create a new npm task for you to just run the tap test (no types and no jest) so that you can have more stable builds.
I ran on a Fedora 34 machine with nodejs 12. I don't see any failures. We'll need more help to recreate the problem.
If you have a machine that you can reliably recreate on and can give me access that might help, as it does not fail on my Fedora 34 machine. What I did was
Which appears to complete without any failures.
@mhdawson But it was tested with nodejs 14 and not nodejs 12
@phracek ok I did not see which node.js version in the posts above. Unfortunately I just retried on the same machine using yum module install nodejs:14
and all the tests still seem to pass.
I got the same error :
Cannot find module '..' from 'node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapterInit.js'
at Resolver.resolveModule (node_modules/jest-resolve/build/resolver.js:324:11)
in my ci pipeline, but not when I try to launch the same test on my computer (even inside the same docker image used by the ci-pipeline).
Without a reproduction, there isn't anything we can do.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
See traceback from our test suite: