1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

test: fix flaky test-debug-port

Browse Source 
It can happen that first data chunk received in stdout is not exactly
`'debug> '`. Make sure the exit condition is met.

PR-URL: https://github.com/nodejs/node/pull/10316
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Italo A. Casas <me@italoacasas.com>
This commit is contained in:
Santiago Gimeno 2016-12-17 09:01:47 +01:00
parent 5d14602181
commit 793d8719eb
No known key found for this signature in database
GPG Key ID: F28C3C8DA33C03BE
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
test/parallel/test-debug-prompt.js
View File

@ -1,13 +1,14 @@
'use strict';
const assert = require('assert');
const common = require('../common');
require('../common');
const spawn = require('child_process').spawn;
const proc = spawn(process.execPath, ['debug', 'foo']);
proc.stdout.setEncoding('utf8');
proc.stdout.once('data', common.mustCall((data) => {
assert.strictEqual(data, 'debug> ');
proc.kill();
}));
let output = '';
proc.stdout.on('data', (data) => {
output += data;
if (output.includes('debug> '))
proc.kill();
});