Skip to content

[chore] Test showing piscina failures in Jest#966

Open
linnerissa wants to merge 7 commits intopiscinajs:currentfrom
linnerissa:nerissa/jest-regression-test
Open

[chore] Test showing piscina failures in Jest#966
linnerissa wants to merge 7 commits intopiscinajs:currentfrom
linnerissa:nerissa/jest-regression-test

Conversation

@linnerissa
Copy link
Contributor

Jest doesnt pass the onWorkerReady message check to execute work after new threads are spun up. Added Jest to show that.

package.json

  • added 3 dev dependencies to support jest tests
  • added commands for jest tests
  • altered CI to include the new jest test

native tests need to skip test/jest subdirectory
added a native version of the new jest test to explicitly force reliance on adding a new thread to pass

…ns in the library. currently fails due to object check on ready message received
…worker thread in order to succeed. similar to jest/ready-message.test.ts
Copy link
Member

@metcoder95 metcoder95 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution! This is super helpful

Can you just add it to the .github/workflows/node.yml as part of the CI?

Signed-off-by: Nerissa Lin <64402413+linnerissa@users.noreply.github.com>
@linnerissa
Copy link
Contributor Author

@metcoder95 i added the test to test:ci. the workflow automatically picks this up in its run tests step.

this approach should be better for local - anyone running test:ci will also run the jest tests. less likely to be surprised by the new jest suite @ pr stage.

@metcoder95 metcoder95 added the backport v5 Backport related with v5.x label Feb 5, 2026
@metcoder95
Copy link
Member

Tests seems failing

@linnerissa linnerissa requested a review from metcoder95 February 6, 2026 04:11
@linnerissa
Copy link
Contributor Author

scripts/run-tests.js ignore parameter actually resolves diff in macos vs windows. changed approach 🙏

@@ -0,0 +1,30 @@
import { resolve } from 'node:path';
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe something is going wrong with the test on windows, but the output on console doesn't seem that helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport v5 Backport related with v5.x

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants