mirror of
https://github.com/nodejs/node.git
synced 2024-11-30 07:27:22 +01:00
c4b5a451e3
Change test so that it passes on the occasional win10 access violation. The workaround here can be undone when issue 5268 is resolved. The test still detects the defect it was written to detect. There are two assertions that detect the defect and only one was disabled. Ref: https://github.com/nodejs/node/issues/5268 Fixes: https://github.com/nodejs/node/issues/4343 PR-URL: https://github.com/nodejs/node/pull/5269 Reviewed-By: James M Snell <jasnell@gmail.com>
27 lines
876 B
JavaScript
27 lines
876 B
JavaScript
'use strict';
|
|
|
|
const common = require('../common');
|
|
const assert = require('assert');
|
|
const spawn = require('child_process').spawn;
|
|
|
|
const args = ['--debug', `--debug-port=${common.PORT}`, '--interactive'];
|
|
const proc = spawn(process.execPath, args);
|
|
proc.stdin.write(`
|
|
util.inspect(Promise.resolve(42));
|
|
util.inspect(Promise.resolve(1337));
|
|
.exit
|
|
`);
|
|
proc.on('exit', common.mustCall((exitCode, signalCode) => {
|
|
// This next line should be included but unfortunately Win10 fails from time
|
|
// to time in CI. See https://github.com/nodejs/node/issues/5268
|
|
// assert.strictEqual(exitCode, 0);
|
|
assert.strictEqual(signalCode, null);
|
|
}));
|
|
let stdout = '';
|
|
proc.stdout.setEncoding('utf8');
|
|
proc.stdout.on('data', (data) => stdout += data);
|
|
process.on('exit', () => {
|
|
assert(stdout.includes('Promise { 42 }'));
|
|
assert(stdout.includes('Promise { 1337 }'));
|
|
});
|