Correct handling of test failures.

Author: ioquatix

.github/workflows/test-coverage.yaml

@@ -73,7 +73,7 @@ jobs:
       timeout-minutes: 10
       env:
         RUBY_VERSION: ${{matrix.ruby}}
-      run: docker-compose -f sentinel/docker-compose.yaml up tests
+      run: docker-compose -f sentinel/docker-compose.yaml up --exit-code-from tests
 
     - uses: actions/upload-artifact@v3
       with:

.github/workflows/test-sentinel.yaml

@@ -38,4 +38,4 @@ jobs:
       timeout-minutes: 10
       env:
         RUBY_VERSION: ${{matrix.ruby}}
-      run: docker-compose -f sentinel/docker-compose.yaml up tests
+      run: docker-compose -f sentinel/docker-compose.yaml up --exit-code-from tests

sentinel/test/async/redis/sentinel_client.rb

@@ -32,19 +32,20 @@
 		expect(client.get(key)).to be == value
 	end
 
-	it "can handle failover" do
-		current_master = client.master
-		
-		client.failover
+	it "should resolve slave address" do
+		client.set(key, value)
 
-		# Failover takes some time to fully complete:
+		# It takes a while to replicate:
 		while true
-			failover_master = client.master
-			break if failover_master['ip'] != current_master['ip']
-			sleep 0.1
+			break if slave_client.get(key) == value
+			sleep 0.01
 		end
 
-		expect(failover_master['ip']).not.to be == current_master['ip']
+		expect(slave_client.get(key)).to be == value
+	end
+	
+	it "can handle failover" do
+		client.failover
 
 		# We can still connect and do stuff:
 		client.set(key, value)