test: fix flaky test-debug-port

It can happen that first data chunk received in stdout is not exactly `'debug> '`. Make sure the exit condition is met. PR-URL: #10316 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Italo A. Casas <[email protected]>
nodejs · Dec 19, 2016 · 793d871 · 793d871
1 parent 5d14602
commit 793d871
Showing 1 changed file with 7 additions and 6 deletions.
diff --git a/test/parallel/test-debug-prompt.js b/test/parallel/test-debug-prompt.js
@@ -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();
+});