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>
34 lines
948 B
JavaScript
34 lines
948 B
JavaScript
'use strict';
|
|
require('../common');
|
|
var assert = require('assert');
|
|
var vm = require('vm');
|
|
|
|
// Test 1: Timeout of 100ms executing endless loop
|
|
assert.throws(function() {
|
|
vm.runInThisContext('while(true) {}', { timeout: 100 });
|
|
});
|
|
|
|
// Test 2: Timeout must be >= 0ms
|
|
assert.throws(function() {
|
|
vm.runInThisContext('', { timeout: -1 });
|
|
}, RangeError);
|
|
|
|
// Test 3: Timeout of 0ms
|
|
assert.throws(function() {
|
|
vm.runInThisContext('', { timeout: 0 });
|
|
}, RangeError);
|
|
|
|
// Test 4: Timeout of 1000ms, script finishes first
|
|
vm.runInThisContext('', { timeout: 1000 });
|
|
|
|
// Test 5: Nested vm timeouts, inner timeout propagates out
|
|
assert.throws(function() {
|
|
var context = {
|
|
log: console.log,
|
|
runInVM: function(timeout) {
|
|
vm.runInNewContext('while(true) {}', context, { timeout: timeout });
|
|
}
|
|
};
|
|
vm.runInNewContext('runInVM(10)', context, { timeout: 100 });
|
|
throw new Error('Test 5 failed');
|
|
}, /Script execution timed out./);
|