Skip to content

The child-process gem fails to spawn processes on Windows #4122

@joankaradimov

Description

@joankaradimov

Environment

jruby version: jruby 9.1.3.0 (2.3.1) 2016-08-29 a2a3b29 Java HotSpot(TM) 64-Bit Server VM 25.66-b18 on 1.8.0_66-b18 +jit [mswin32-x86_64]
OS: Windows 10
childprocess version: 0.5.9

Expected Behavior

Running:

gem 'childprocess'
require 'childprocess'
cp = ChildProcess.new('notepad.exe')
cp.start # errors

... should spawn a new process. This works on jruby 9.1.2.0

Actual Behavior

This exception is raised:

ChildProcess::Error: Unknown error (Windows says "The operation completed successfully.", but it did not.)
        from C:/dev/jruby-9.1.3.0/lib/ruby/gems/shared/gems/childprocess-0.5.9/lib/childprocess/windows/lib.rb:325:in `handle_for'
        from C:/dev/jruby-9.1.3.0/lib/ruby/gems/shared/gems/childprocess-0.5.9/lib/childprocess/jruby.rb:48:in `windows_handle_for'
        from C:/dev/jruby-9.1.3.0/lib/ruby/gems/shared/gems/childprocess-0.5.9/lib/childprocess/windows/lib.rb:306:in `handle_for'
        from C:/dev/jruby-9.1.3.0/lib/ruby/gems/shared/gems/childprocess-0.5.9/lib/childprocess/windows/process_builder.rb:137:in `std_stream_handle_for'
        from C:/dev/jruby-9.1.3.0/lib/ruby/gems/shared/gems/childprocess-0.5.9/lib/childprocess/windows/process_builder.rb:132:in `setup_io'
        from C:/dev/jruby-9.1.3.0/lib/ruby/gems/shared/gems/childprocess-0.5.9/lib/childprocess/windows/process_builder.rb:32:in `start'
        from C:/dev/jruby-9.1.3.0/lib/ruby/gems/shared/gems/childprocess-0.5.9/lib/childprocess/windows/process.rb:69:in `launch_process'
        from C:/dev/jruby-9.1.3.0/lib/ruby/gems/shared/gems/childprocess-0.5.9/lib/childprocess/abstract_process.rb:82:in `start'
        from (irb):4:in `<eval>'
        from org/jruby/RubyKernel.java:994:in `eval'
        from org/jruby/RubyKernel.java:1295:in `loop'
        from org/jruby/RubyKernel.java:1114:in `catch'
        from org/jruby/RubyKernel.java:1114:in `catch'
        from C:/dev/jruby-9.1.3.0/bin/jirb:13:in `<main>'

Notes

I noticed that issue #2598 has an identical error message.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions