-
Type:
Task
-
Resolution: Fixed
-
Priority:
Minor - P4
-
Affects Version/s: None
-
Component/s: None
-
None
-
Networking & Observability
-
Fully Compatible
-
N&O 2025-09-15, N&O 2025-09-29
-
0
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When the "assert.soon" fails in "rejected_connection_pool_request.js", there's no way to know how the actual values differed from the expected value. Add logging to reveal that.
Also, increase the timeout for that "assert.soon". This test hasn't failed since July, but a little more wiggle room is unlikely to hurt.