Rephrase comments in integration test and fork_runner

Author: benoittgt

lib/rspec/core/bisect/fork_runner.rb

@@ -92,10 +92,8 @@ def initialize(runner, channel)
 
           def dispatch_specs(run_descriptor)
             fork { run_specs(run_descriptor) }
-            # We don't wait anymore that the subprocess is done with a waitpid
-            # because there is no need to. On OSX and Linux, with more than
-            # 1548 tests we were filling-up the pipe and saturating it. This
-            # ended up with stuck bisect command.
+            # We don't use Process.waitpid here as it was causing bisects to
+            # block due to the file descriptor limit on OSX / Linux.
           end
 
         private

spec/integration/bisect_spec.rb

@@ -33,12 +33,10 @@ def bisect(cli_args, expected_status=nil)
       end
     end
 
-    context "when the bisect command is long" do
-      # On OSX and Linux when we have many tests we could had pipe size issue. We did not empty the buffer
-      # and we ended up with a pipe that was full and it was blocking the main process. This made the bisect
-      # command stuck without further information. This test run blocking_pipe_bisect_spec.rb_ that
-      # will ensure that we are not blocked anymore in this kind of situation.
-      # https://github.com/rspec/rspec-core/pull/2669
+    context "when the bisect commasaturingnd is long" do
+      # On OSX and Linux a file descriptor limit meant that the bisect process got stuck at a certain limit.
+      # This test demonstrates that we can run large bisects above this limit (found to be at time of commit).
+      # See: https://github.com/rspec/rspec-core/pull/2669
       it 'does not hit pipe size limit and does not get stuck' do
         output = bisect(%W[spec/rspec/core/resources/blocking_pipe_bisect_spec.rb_], 1)
         expect(output).to include("No failures found.")