Skip to content

tests fail in bash on Windows 10 #11

@catdad

Description

@catdad

Tried on Node 4.4.2, 6.4.0, 6.5.0.

  [Spawn]
    ✓ executes a string command
    ✓ executes a command with a full options object
    ✓ takes a cwd
    ✓ takes an env
    ✓ can execute NPM modules from bin when env is set (543ms)
    ✓ does not crash on a process stream (94ms)
    streams to
      ✓ an stdout stream
      ✓ an stderr stream
    streams from
      1) an stdin stream
    calls a callback
      ✓ with err if the command does not exist
      ✓ with an stdout parameter
      ✓ with an stderr parameter
      ✓ with nothing, when no callback is specified
      ✓ provides stdio streams even when there is an error (97ms)

  [Exec]
    ✓ executes a string command
    ✓ executes a command with a full options object
    ✓ takes a cwd
    ✓ takes an env
    ✓ can execute NPM modules from bin when env is set (535ms)
    ✓ does not crash on a process stream (94ms)
    streams to
      ✓ an stdout stream
      ✓ an stderr stream
    streams from
      2) an stdin stream
    calls a callback
      ✓ with err if the command does not exist
      ✓ with an stdout parameter
      ✓ with an stderr parameter
      ✓ with nothing, when no callback is specified
      ✓ provides stdio streams even when there is an error (95ms)

  [env]
    ✓ returns a copy of process.env
    ✓ extends process.env with the provided object
    ✓ does not modify the actual process.env


  29 passing (2s)
  2 failing

  1) [Spawn] streams from an stdin stream:
     Uncaught AssertionError: expected [Error: Process exited with code: 1] to be falsy
      at testSuccessResult (test/main.test.js:19:30)
      at test/main.test.js:172:21
      at shellton.js:157:9
      at node_modules/async/lib/async.js:726:13
      at node_modules/async/lib/async.js:52:16
      at done (node_modules/async/lib/async.js:241:17)
      at node_modules/async/lib/async.js:44:16
      at node_modules/async/lib/async.js:723:17
      at node_modules/async/lib/async.js:167:37
      at ChildProcess.<anonymous> (shellton.js:141:17)
      at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)

  2) [Exec] streams from an stdin stream:
     Uncaught expected [Error: Command failed: node -e "process.stdin.pipe(process.stdout)"
internal/process/stdio.js:82
        throw new Error('Implement me. Unknown stdin file type!');
        ^

Error: Implement me. Unknown stdin file type!
    at process.getStdin [as stdin] (internal/process/stdio.js:82:15)
    at [eval]:1:8
    at ContextifyScript.Script.runInThisContext (vm.js:25:33)
    at Object.exports.runInThisContext (vm.js:77:17)
    at Object.<anonymous> ([eval]-wrapper:6:22)
    at Module._compile (module.js:556:32)
    at bootstrap_node.js:357:29
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
    at process._tickCallback (internal/process/next_tick.js:98:9)
] to be falsy
  AssertionError: expected [Error: Command failed: node -e "process.stdin.pipe(process.stdout)"
  internal/process/stdio.js:82
          throw new Error('Implement me. Unknown stdin file type!');
          ^

  Error: Implement me. Unknown stdin file type!
      at process.getStdin [as stdin] (internal/process/stdio.js:82:15)
      at [eval]:1:8
      at ContextifyScript.Script.runInThisContext (vm.js:25:33)
      at Object.exports.runInThisContext (vm.js:77:17)
      at Object.<anonymous> ([eval]-wrapper:6:22)
      at bootstrap_node.js:357:29
      at _combinedTickCallback (internal/process/next_tick.js:67:7)
      at process._tickCallback (internal/process/next_tick.js:98:9)
  ] to be falsy
      at testSuccessResult (test/main.test.js:19:30)
      at test/main.test.js:172:21
      at shellton.js:77:9
      at ChildProcess.exithandler (child_process.js:213:5)
      at maybeClose (internal/child_process.js:877:16)
      at Socket.<anonymous> (internal/child_process.js:334:11)
      at Pipe._handle.close [as _onclose] (net.js:493:12)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions