Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Incomplete
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:
      jruby 1.6.0.RC1 (ruby 1.8.7 patchlevel 330) (2011-01-22 5410dc0) (Java HotSpot(TM) Client VM 1.6.0_10) [Windows XP-x86-java]
    • Testcase included:
      yes
    • Number of attachments :
      0

      Description

      >> a = IO.popen("ruby.exe -e sleep")
      => #<IO:0x1fb050c>
      >> a.close # this call should never return
      => nil
      >> $?
      => #<Process::Status: pid=????,exited(1)>

      You'll notice that it returns prematurely. This works with 1.5.5, but not HEAD. Not sure if this is an issue on Linux as well or not.
      Cheers!
      -r

        Activity

        Hide
        Hiro Asari added a comment -

        This occurs on OS X as well.

        $ jruby -ve 'a=IO.popen("jruby -e sleep"); a.close; p $?'
        jruby 1.6.0.RC1 (ruby 1.8.7 patchlevel 330) (2011-01-25 04ce8b7) (Java HotSpot(TM) 64-Bit Server VM 1.6.0_22) [darwin-x86_64-java]
        #<Process::Status: pid=????,exited(143)>
        
        Show
        Hiro Asari added a comment - This occurs on OS X as well. $ jruby -ve 'a=IO.popen("jruby -e sleep"); a.close; p $?' jruby 1.6.0.RC1 (ruby 1.8.7 patchlevel 330) (2011-01-25 04ce8b7) (Java HotSpot(TM) 64-Bit Server VM 1.6.0_22) [darwin-x86_64-java] #<Process::Status: pid=????,exited(143)>
        Hide
        Charles Oliver Nutter added a comment -

        JRuby has moved bug tracking to Github, accessible via our Github page at https://github.com/jruby/jruby/issues, or via http://bugs.jruby.org. In addition, this bug has not been updated in over two years.

        We have decided to close down these old JIRA issues.

        If your report is still a problem on current JRuby versions (1.7.18 or master/9.0.0.0), please re-file the bug at http://bugs.jruby.org.

        You can contact us on the JRuby mailing lists, Freenode IRC channel #jruby, or the @jruby Twitter account if you are unsure how to proceed.

        Show
        Charles Oliver Nutter added a comment - JRuby has moved bug tracking to Github, accessible via our Github page at https://github.com/jruby/jruby/issues , or via http://bugs.jruby.org . In addition, this bug has not been updated in over two years. We have decided to close down these old JIRA issues. If your report is still a problem on current JRuby versions (1.7.18 or master/9.0.0.0), please re-file the bug at http://bugs.jruby.org . You can contact us on the JRuby mailing lists, Freenode IRC channel #jruby, or the @jruby Twitter account if you are unsure how to proceed.

          People

          • Assignee:
            Thomas E Enebo
            Reporter:
            Roger Pack

            Dates

            • Created:
              Updated:
              Resolved: