test: fix test-cli-syntax assertions on windows

The test introduced in a5f91ab accidentally introduced failures on some windows builds. Update the assertion that was causing the failures. PR-URL: #12212 Ref: #11689 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]>
nodejs · Apr 4, 2017 · 9348f31 · 9348f31
1 parent c79b081
commit 9348f31
Showing 1 changed file with 4 additions and 3 deletions.
diff --git a/test/parallel/test-cli-syntax.js b/test/parallel/test-cli-syntax.js
@@ -124,9 +124,10 @@ syntaxArgs.forEach(function(args) {
     const args = [checkFlag, evalFlag, 'foo'];
     const c = spawnSync(node, args, {encoding: 'utf8'});
 
-    assert.strictEqual(
-      c.stderr,
-      `${node}: either --check or --eval can be used, not both\n`
+    assert(
+      c.stderr.startsWith(
+        `${node}: either --check or --eval can be used, not both`
+      )
     );
 
     assert.strictEqual(c.status, 9, 'code === ' + c.status);