From f74aece0be7ff03f523a99ceb7e0e0f8674cb2ce Mon Sep 17 00:00:00 2001
From: Ivo Anjo <ivo.anjo@ist.utl.pt>
Date: Sat, 23 Jun 2018 19:45:08 +0100
Subject: [PATCH] Fix wrong expected exception in spec assertion

It's pretty straightforward that an `ArgumentError` is raised here.
I wonder if this was changed to `RejectedExecutionError` because
somehow that was happening instead due to cross-spec interference.
---
 spec/concurrent/channel_spec.rb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/spec/concurrent/channel_spec.rb b/spec/concurrent/channel_spec.rb
index 62bc69efc..abe4bb8f4 100644
--- a/spec/concurrent/channel_spec.rb
+++ b/spec/concurrent/channel_spec.rb
@@ -595,7 +595,7 @@ module Concurrent
         it 'raises an exception when no block is given' do
           expect {
             Channel.go_loop
-          }.to raise_error(RejectedExecutionError)
+          }.to raise_error(ArgumentError)
         end
 
         it 'loops until the block returns false' do