d795301025
common.js needs to be loaded in all tests so that there is checking for variable leaks and possibly other things. However, it does not need to be assigned to a variable if nothing in common.js is referred to elsewhere in the test. The main tradeoff for this bit of code churn is that it gets the code base most of the way to being able to enable the no-unused-vars rule in eslint. (The non-tooling benefit is that it lessens cognitive load when reading tests as it is an immediate indication that none of the functions or properties in common.js will be used by the test.) PR-URL: https://github.com/nodejs/node/pull/4563 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
44 lines
1 KiB
JavaScript
44 lines
1 KiB
JavaScript
'use strict';
|
|
// This example attempts to time out before the connection is established
|
|
// https://groups.google.com/forum/#!topic/nodejs/UE0ZbfLt6t8
|
|
// https://groups.google.com/forum/#!topic/nodejs-dev/jR7-5UDqXkw
|
|
|
|
require('../common');
|
|
var net = require('net');
|
|
var assert = require('assert');
|
|
|
|
var start = new Date();
|
|
|
|
var gotTimeout = false;
|
|
|
|
var gotConnect = false;
|
|
|
|
var T = 100;
|
|
|
|
// 192.0.2.1 is part of subnet assigned as "TEST-NET" in RFC 5737.
|
|
// For use solely in documentation and example source code.
|
|
// In short, it should be unreachable.
|
|
// In practice, it's a network black hole.
|
|
var socket = net.createConnection(9999, '192.0.2.1');
|
|
|
|
socket.setTimeout(T);
|
|
|
|
socket.on('timeout', function() {
|
|
console.error('timeout');
|
|
gotTimeout = true;
|
|
var now = new Date();
|
|
assert.ok(now - start < T + 500);
|
|
socket.destroy();
|
|
});
|
|
|
|
socket.on('connect', function() {
|
|
console.error('connect');
|
|
gotConnect = true;
|
|
socket.destroy();
|
|
});
|
|
|
|
|
|
process.on('exit', function() {
|
|
assert.ok(gotTimeout);
|
|
assert.ok(!gotConnect);
|
|
});
|