Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: increase coverage for worker_threads #22942

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions test/parallel/test-worker-onmessage-not-a-function.js
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
// When MessagePort.onmessage is set to a value that is not a function, the
// setter should call .unref() and .stop(), clearing a previous onmessage
// listener from holding the event loop open. This test confirms that
// functionality.

// Flags: --experimental-worker
'use strict';
const common = require('../common');
const { Worker, parentPort } = require('worker_threads');

// Do not use isMainThread so that this test itself can be run inside a Worker.
if (!process.env.HAS_STARTED_WORKER) {
process.env.HAS_STARTED_WORKER = 1;
const w = new Worker(__filename);
w.postMessage(2);
} else {
// .onmessage uses a setter. Set .onmessage to a function that ultimately
// should not be called. This will call .ref() and .start() which will keep
// the event loop open (and prevent this from exiting) if the subsequent
// assignment of a value to .onmessage doesn't call .unref() and .stop().
parentPort.onmessage = common.mustNotCall();
// Setting `onmessage` to a value that is not a function should clear the
// previous value and also should allow the event loop to exit. (In other
// words, this test should exit rather than run indefinitely.)
parentPort.onmessage = 'fhqwhgads';
}