From 1fb397f730b209edaff995f9cc411a5d8ed2d65f Mon Sep 17 00:00:00 2001 From: Jacob Champion Date: Wed, 17 Jun 2026 09:57:15 -0700 Subject: [PATCH] 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 c0dafb8be76..95693fcdb18 100644 --- a/src/test/modules/oauth_validator/t/001_server.pl +++ b/src/test/modules/oauth_validator/t/001_server.pl @@ -444,7 +444,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