8caa1dcee6
There are several cleanups here that are not just style nits... 1. The `common.isMainThread` was just a passthrough to the `isMainThread` export on the worker_thread module. It's use was inconsistent and just obfuscated the fact that the test file depend on the `worker_threads` built-in. By eliminating it we simplify the test harness a bit and make it clearer which tests depend on the worker_threads check. 2. The `common.isDumbTerminal` is fairly unnecesary since that just wraps a public API check. 3. Several of the `common.skipIf....` checks were inconsistently used and really don't need to be separate utility functions. A key part of the motivation here is to work towards making more of the tests more self-contained and less reliant on the common test harness where possible. PR-URL: https://github.com/nodejs/node/pull/56712 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
33 lines
900 B
JavaScript
33 lines
900 B
JavaScript
'use strict';
|
|
|
|
// Regression test for https://github.com/nodejs/node/issues/13262
|
|
|
|
const common = require('../common');
|
|
const assert = require('assert');
|
|
const async_hooks = require('async_hooks');
|
|
const { isMainThread } = require('worker_threads');
|
|
|
|
if (!isMainThread) {
|
|
common.skip('Worker bootstrapping works differently -> different async IDs');
|
|
}
|
|
|
|
let seenId, seenResource;
|
|
|
|
async_hooks.createHook({
|
|
init: common.mustCall((id, provider, triggerAsyncId, resource) => {
|
|
seenId = id;
|
|
seenResource = resource;
|
|
assert.strictEqual(provider, 'Immediate');
|
|
assert.strictEqual(triggerAsyncId, 1);
|
|
}),
|
|
before: common.mustNotCall(),
|
|
after: common.mustNotCall(),
|
|
destroy: common.mustCall((id) => {
|
|
assert.strictEqual(seenId, id);
|
|
})
|
|
}).enable();
|
|
|
|
const immediate = setImmediate(common.mustNotCall());
|
|
assert.strictEqual(immediate, seenResource);
|
|
clearImmediate(immediate);
|