test: fix test-cli-syntax assertions on windows

The test introduced in a5f91ab230c574d561780b6867d00f06fcc1e4de
accidentally introduced failures on some windows builds. Update the
assertion that was causing the failures.

PR-URL: https://github.com/nodejs/node/pull/12212
Ref: https://github.com/nodejs/node/pull/11689
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
This commit is contained in:
Teddy Katz 2017-04-04 11:09:31 -04:00
parent c79b081367
commit 9348f31c2a
No known key found for this signature in database
GPG Key ID: B79EC7ABC0AA53A0

View File

@ -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);