0001-oauth_validator-Print-captured-stderr-after-call-cou.patch

From 04185692ec6297e7354626ac54b8e6c1ca22361b Mon Sep 17 00:00:00 2001
From: Jacob Champion <jacob.champion@enterprisedb.com>
Date: Mon, 15 Jun 2026 14:25:28 -0700
Subject: [PATCH 1/3] oauth_validator: Print captured stderr after call-count
 failure

If the call count test fails, you'll reasonably want to know what the
network trace looked like, but that information is currently swallowed.
Print it out instead.

Backpatch-through: 18
---
 src/test/modules/oauth_validator/t/001_server.pl | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/src/test/modules/oauth_validator/t/001_server.pl b/src/test/modules/oauth_validator/t/001_server.pl
index 1619fbffd45..0d7618a5ef1 100644
--- a/src/test/modules/oauth_validator/t/001_server.pl
+++ b/src/test/modules/oauth_validator/t/001_server.pl
@@ -518,7 +518,10 @@ if (like($stderr, $count_pattern, "call count: count is printed"))
 	# to change across OSes and Curl updates, we're likely in trouble if we see
 	# hundreds or thousands of calls.
 	$stderr =~ $count_pattern;
-	cmp_ok($1, '<', 100, "call count is reasonably small");
+	unless (cmp_ok($1, '<', 100, "call count is reasonably small"))
+	{
+		diag "full stderr:\n$stderr";
+	}
 }
 
 # Stress test: make sure our builtin flow operates correctly even if the client
-- 
2.34.1