Deal with JRuby signal handling asynchronicity.

Author: myronmarston

spec/integration/bisect_spec.rb

@@ -125,20 +125,32 @@ def bisect_round_finished(notification)
         ))
 
         output = normalize_durations(formatter_output.string)
-
-        expect(output).to eq(<<-EOS.gsub(/^\s+\|/, ''))
+        expected_start = <<-EOS.gsub(/^\s+\|/, '')
           |Bisect started using options: "spec/rspec/core/resources/order_dependent_specs.rb --order defined"
           |Running suite to find failures... (n.nnnn seconds)
           |Starting bisect with 1 failed example and 21 non-failing examples.
           |
           |Round 1: searching for 11 non-failing examples (of 21) to ignore: .. (n.nnnn seconds)
           |Round 2: searching for 6 non-failing examples (of 11) to ignore: .
+        EOS
+
+        expected_end = <<-EOS.gsub(/^\s+\|/, '')
           |
           |Bisect aborted!
           |
           |The most minimal reproduction command discovered so far is:
           |  rspec ./spec/rspec/core/resources/order_dependent_specs.rb[7:1,8:1,9:1,10:1,11:1,22:1] --order defined
         EOS
+
+        if RSpec::Support::Ruby.jruby?
+          # For some reason, on JRuby the `Round 3:` line is also included, even though
+          # we send SIGINT at the end of Round 2. It appears that Signal handling is
+          # asynchronous on JRuby (maybe it happens in another thread?).
+          expect(output).to start_with(expected_start.chomp).and end_with(expected_end)
+        else
+          # On MRI, the entire output is these two parts, as expected.
+          expect(output).to eq(expected_start + expected_end)
+        end
       end
     end
   end