mirror of
https://github.com/nodejs/node.git
synced 2025-05-01 08:42:45 +00:00

Async wrap providers tested: - crypto.randomBytes - crypto.pbkdf2 - fs event wrap - fsreqwrap access - fsreqwrap readFile - getaddrinforeq wrap - getnameinforeq wrap - pipe connect wrap - query wrap - pipewrap - processwrap - shutdown wrap - tcpwrap - udpwrap - send wrap - detailed signal wrap - statwatcher - timerwrap via setTimeout - timerwrap via setInterval - for Immediate - http parser request - http parser response - connection via ssl server - tls wrap - write wrap - ttywrap via readstream - ttywrap via wriream - zctx via zlib binding deflate Embedder API: - async-event tests - one test looks at the happy paths - another ensures that in cases of events emitted in an order that doesn't make sense, the order is enforced by async hooks throwing a meaningful error - embedder enforcement tests are split up since async hook stack corruption now the process - therefore we launch a child and check for error output of the offending code Additional tests: - tests that show that we can enable/disable hooks inside their lifetime events - tests that verify the graph of resources triggering the creation of other resources Test Helpers: - init-hooks: - returns one collector instance - when created an async hook is created and the lifetime events are registered to call the appropriate collector functions - the collector also exposes `enable` and `disable` functions which call through to the async hook - hook checks: - checks invocations of life time hooks against the actual invocations that were collected - in some cases like `destroy` a min/max range of invocations can be supplied since in these cases the exact number is non-deterministic - verify graph: - verifies the triggerIds of specific async resources are as expected, i.e. the creation of resources was triggered by the resource we expect - includes a printGraph function to generate easily readable test input for verify graph - both functions prune TickObjects to create less brittle and easier to understand tests PR-URL: https://github.com/nodejs/node/pull/12892 Ref: https://github.com/nodejs/node/pull/11883 Ref: https://github.com/nodejs/node/pull/8531 Reviewed-By: Andreas Madsen <amwebdk@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Sam Roberts <vieuxtech@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
105 lines
3.8 KiB
JavaScript
105 lines
3.8 KiB
JavaScript
'use strict';
|
|
|
|
const common = require('../common');
|
|
const assert = require('assert');
|
|
const tick = require('./tick');
|
|
const initHooks = require('./init-hooks');
|
|
const { checkInvocations } = require('./hook-checks');
|
|
|
|
const net = require('net');
|
|
|
|
common.refreshTmpDir();
|
|
|
|
const hooks = initHooks();
|
|
hooks.enable();
|
|
let pipe1, pipe2, pipe3;
|
|
let pipeconnect;
|
|
|
|
net.createServer(common.mustCall(function(c) {
|
|
c.end();
|
|
this.close();
|
|
process.nextTick(maybeOnconnect.bind(null, 'server'));
|
|
})).listen(common.PIPE, common.mustCall(onlisten));
|
|
|
|
function onlisten() {
|
|
let pipes = hooks.activitiesOfTypes('PIPEWRAP');
|
|
let pipeconnects = hooks.activitiesOfTypes('PIPECONNECTWRAP');
|
|
assert.strictEqual(
|
|
pipes.length, 1,
|
|
'one pipe wrap created when net server is listening');
|
|
assert.strictEqual(
|
|
pipeconnects.length, 0,
|
|
'no pipeconnect wrap created when net server is listening');
|
|
|
|
net.connect(common.PIPE,
|
|
common.mustCall(maybeOnconnect.bind(null, 'client')));
|
|
|
|
pipes = hooks.activitiesOfTypes('PIPEWRAP');
|
|
pipeconnects = hooks.activitiesOfTypes('PIPECONNECTWRAP');
|
|
assert.strictEqual(pipes.length, 2,
|
|
'2 pipe wraps created when connecting client');
|
|
assert.strictEqual(pipeconnects.length, 1,
|
|
'1 connectwrap created when connecting client');
|
|
|
|
pipe1 = pipes[0];
|
|
pipe2 = pipes[1];
|
|
pipeconnect = pipeconnects[0];
|
|
|
|
assert.strictEqual(pipe1.type, 'PIPEWRAP', 'first is pipe wrap');
|
|
assert.strictEqual(pipe2.type, 'PIPEWRAP', 'second is pipe wrap');
|
|
assert.strictEqual(pipeconnect.type, 'PIPECONNECTWRAP',
|
|
'third is pipeconnect wrap');
|
|
[ pipe1, pipe2, pipeconnect ].forEach(check);
|
|
|
|
function check(a) {
|
|
assert.strictEqual(typeof a.uid, 'number', 'uid is a number');
|
|
assert.strictEqual(typeof a.triggerId, 'number', 'triggerId is a number');
|
|
checkInvocations(a, { init: 1 }, 'after net.connect');
|
|
}
|
|
}
|
|
|
|
const awaitOnconnectCalls = new Set(['server', 'client']);
|
|
function maybeOnconnect(source) {
|
|
// both server and client must call onconnect. On most OS's waiting for
|
|
// the client is sufficient, but on CertOS 5 the sever needs to respond too.
|
|
assert.ok(awaitOnconnectCalls.size > 0);
|
|
awaitOnconnectCalls.delete(source);
|
|
if (awaitOnconnectCalls.size > 0) return;
|
|
|
|
const pipes = hooks.activitiesOfTypes('PIPEWRAP');
|
|
const pipeconnects = hooks.activitiesOfTypes('PIPECONNECTWRAP');
|
|
|
|
assert.strictEqual(pipes.length, 3,
|
|
'3 pipe wraps created when client connected');
|
|
assert.strictEqual(pipeconnects.length, 1,
|
|
'1 connectwrap created when client connected');
|
|
pipe3 = pipes[2];
|
|
assert.strictEqual(typeof pipe3.uid, 'number', 'uid is a number');
|
|
assert.strictEqual(typeof pipe3.triggerId, 'number', 'triggerId is a number');
|
|
|
|
checkInvocations(pipe1, { init: 1, before: 1, after: 1 },
|
|
'pipe1, client connected');
|
|
checkInvocations(pipe2, { init: 1 }, 'pipe2, client connected');
|
|
checkInvocations(pipeconnect, { init: 1, before: 1 },
|
|
'pipeconnect, client connected');
|
|
checkInvocations(pipe3, { init: 1 }, 'pipe3, client connected');
|
|
tick(5);
|
|
}
|
|
|
|
process.on('exit', onexit);
|
|
|
|
function onexit() {
|
|
hooks.disable();
|
|
hooks.sanityCheck('PIPEWRAP');
|
|
hooks.sanityCheck('PIPECONNECTWRAP');
|
|
// TODO(thlorenz) why have some of those 'before' and 'after' called twice
|
|
checkInvocations(pipe1, { init: 1, before: 1, after: 1, destroy: 1 },
|
|
'pipe1, process exiting');
|
|
checkInvocations(pipe2, { init: 1, before: 2, after: 2, destroy: 1 },
|
|
'pipe2, process exiting');
|
|
checkInvocations(pipeconnect, { init: 1, before: 1, after: 1, destroy: 1 },
|
|
'pipeconnect, process exiting');
|
|
checkInvocations(pipe3, { init: 1, before: 2, after: 2, destroy: 1 },
|
|
'pipe3, process exiting');
|
|
}
|