Change in behavior for Zeek's broker.ssl_auth_failure after recent changes
Neverlord opened this issue · comments
With 92b4287, we've dropped the maximum retry limit again.
After that change, Zeek's broker.ssl_auth_failure btest started failing. It's waiting for an error event that is supposed to trigger for a failed connection attempt. Those events should be emitted by Broker and a first spot-check with broker-benchmark had them appear. However, maybe that's not the case for all error conditions. There's a workaround on the Zeek side (zeek/zeek#2372), but the test should've continued to run without modification.