mirror of
https://github.com/ruby/ruby.git
synced 2022-11-09 12:17:21 -05:00
92f5653f45
It is possible to have both MJIT and normal child processes alive, so we cannot set ECHILD based on such a guess. We can still elide waitpid(PID <= 0) calls if we have callers in vm->waiting_pids, however. For specs, ensure Process.waitall does not leak MJIT PIDs to Rubyspace. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@63764 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
40 lines
1.3 KiB
Ruby
40 lines
1.3 KiB
Ruby
require_relative '../../spec_helper'
|
|
|
|
describe "Process.wait2" do
|
|
before :all do
|
|
# HACK: this kludge is temporarily necessary because some
|
|
# misbehaving spec somewhere else does not clear processes
|
|
# Note: background processes are unavoidable with MJIT,
|
|
# but we shouldn't reap them from Ruby-space
|
|
begin
|
|
Process.wait(-1, Process::WNOHANG)
|
|
without_feature :mjit do
|
|
$stderr.puts "Leaked process before wait2 specs! Waiting for it"
|
|
end
|
|
leaked = Process.waitall
|
|
$stderr.puts "leaked before wait2 specs: #{leaked}" unless leaked.empty?
|
|
with_feature :mjit do
|
|
# Ruby-space should not see PIDs used by mjit
|
|
leaked.should be_empty
|
|
end
|
|
rescue Errno::ECHILD # No child processes
|
|
rescue NotImplementedError
|
|
end
|
|
end
|
|
|
|
platform_is_not :windows do
|
|
it "returns the pid and status of child process" do
|
|
pidf = Process.fork { Process.exit! 99 }
|
|
results = Process.wait2
|
|
results.size.should == 2
|
|
pidw, status = results
|
|
pidf.should == pidw
|
|
status.exitstatus.should == 99
|
|
end
|
|
end
|
|
|
|
it "raises a StandardError if no child processes exist" do
|
|
lambda { Process.wait2 }.should raise_error(Errno::ECHILD)
|
|
lambda { Process.wait2 }.should raise_error(StandardError)
|
|
end
|
|
end
|