Remove message parameter from env.assertTrue calls

The RLTest framework's assertTrue() method doesn't accept
a message parameter in the same way as standard unittest.
Removed all message parameters and added debugPrint calls
before assertions to provide context when tests fail.

This fixes the 'can only concatenate str (not int) to str'
TypeError that was occurring.

Author: fcostaoliveira

tests/test_reconnections.py

@@ -126,16 +126,13 @@ def client_killer():
         env.debugPrint("Total clients killed: {}".format(kill_count[0]), True)
 
         # Verify that we actually killed some connections
-        env.assertTrue(
-            kill_count[0] > 0, "Expected to kill at least one client connection"
-        )
+        if kill_count[0] == 0:
+            env.debugPrint("WARNING: No clients were killed during the test", True)
+        env.assertTrue(kill_count[0] > 0)
 
         # Verify memtier completed successfully despite connection kills
         debugPrintMemtierOnError(config, env)
-        env.assertTrue(
-            memtier_ok == True,
-            "memtier_benchmark should complete successfully with reconnections",
-        )
+        env.assertTrue(memtier_ok == True)
 
         # Verify output files exist
         env.assertTrue(os.path.isfile("{0}/mb.stdout".format(config.results_dir)))
@@ -146,11 +143,10 @@ def client_killer():
         with open("{0}/mb.stderr".format(config.results_dir)) as stderr:
             stderr_content = stderr.read()
             # Should see reconnection attempt messages
-            env.assertTrue(
-                "reconnection" in stderr_content.lower()
-                or "reconnect" in stderr_content.lower(),
-                "Expected to see reconnection messages in stderr",
-            )
+            has_reconnect_msg = "reconnection" in stderr_content.lower() or "reconnect" in stderr_content.lower()
+            if not has_reconnect_msg:
+                env.debugPrint("WARNING: No reconnection messages found in stderr", True)
+            env.assertTrue(has_reconnect_msg)
 
         # Verify that some requests were completed
         # (we may not get the exact expected count due to reconnections, but should get some)
@@ -161,7 +157,9 @@ def client_killer():
         overall_request_count = agg_info_commandstats(
             master_nodes_connections, merged_command_stats
         )
-        env.assertTrue(overall_request_count > 0, "Expected some requests to complete")
+        if overall_request_count == 0:
+            env.debugPrint("WARNING: No requests completed", True)
+        env.assertTrue(overall_request_count > 0)
 
     finally:
         # Make sure to stop the killer thread
@@ -267,4 +265,6 @@ def test_reconnect_disabled_by_default(env):
     # Note: This test might be flaky if the connection is killed after all work is done
     # So we just verify the test completes one way or another
     env.debugPrint("memtier exit code: {}".format(return_code), True)
-    env.assertTrue(killed, "Expected to kill at least one connection")
+    if not killed:
+        env.debugPrint("WARNING: No connections were killed", True)
+    env.assertTrue(killed)