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
…irector`.
Note that the tests won’t run properly in Node.js v18 until the fix for this Node.js test runner bug is published in a v18 release:
nodejs/node#48845
jaydenseric
added a commit
to jaydenseric/next-graphql-react
that referenced
this issue
Nov 21, 2023
TODO: Re-enable these tests in Node.js v18 once the fix for this Node.js test runner bug is published in a v18 release:
nodejs/node#48845
The Node.js v18.19.0 release is scheduled for 2023-11-28:
nodejs/Release#737
Version
v20.4.0
Platform
Darwin lucille.lan 22.5.0 Darwin Kernel Version 22.5.0: Thu Jun 8 22:22:23 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T6020 arm64
Subsystem
test runner
What steps will reproduce the bug?
Running this with
node --test
leads to the error "test could not be started because its parent finished"How often does it reproduce? Is there a required condition?
It's deterministic.
What is the expected behavior? Why is that the expected behavior?
describe
's documentation indicates that an async function can be passed, so it should be awaited.What do you see instead?
I get the error
test could not be started because its parent finished
.Additional information
No response
The text was updated successfully, but these errors were encountered: