Running npm run test causes these errors to occur, which causes failures in unrelated modules. The failing test suites fun without error when run in isolation however.
From what I can tell, it seems to be related to the WorkerManager @CMCDragonkai
A worker process has failed to exit gracefully and has been force exited. This is likely caused by tests leaking due to improper teardown. Try running with --detectOpenHandles to find leaks.
Summary of all failing tests
FAIL tests/PolykeyAgent.test.ts (26.341 s)
● Polykey › async start constructs node path
Timeout: Did not receive an init message from worker after 10000ms. Make sure the worker calls expose().
at Timeout._onTimeout (node_modules/threads/dist/master/spawn.js:35:53)
● Polykey › async stop leaves the node path
Timeout: Did not receive an init message from worker after 10000ms. Make sure the worker calls expose().
at Timeout._onTimeout (node_modules/threads/dist/master/spawn.js:35:53)
FAIL tests/bin/polykey.test.ts (41.051 s)
● CLI echoes › should echo
Timeout: Did not receive an init message from worker after 10000ms. Make sure the worker calls expose().
at Timeout._onTimeout (node_modules/threads/dist/master/spawn.js:35:53)
Running
npm run testcauses these errors to occur, which causes failures in unrelated modules. The failing test suites fun without error when run in isolation however.From what I can tell, it seems to be related to the
WorkerManager@CMCDragonkai