Michał Kępień 48e705d738 Account for idle timeouts in the "dispatch" test ... When the tests-connreset.py module was initially implemented in commit 5c17919019, the dispatch code did not properly apply the idle timeout to TCP connections. This allowed the check in that test module to reset the TCP connection after 5 seconds as named did not attempt to tear the connection down earlier than that. However, as the dispatch code was improved, the idle timeout started being enforced for TCP dispatches; the exact value it is set to in the current code depends on a given server's SRTT, but it defaults to about 1.2 seconds for responsive servers. This means that the code paths triggered by the "dispatch" system test are now different than the ones it was originally supposed to trigger because it is now named itself that shuts the TCP connection down cleanly before the ans3 server gets a chance to reset it. Account for the above by lowering the amount of time after which the ans3 server in the "dispatch" system test resets TCP connections to just 1 second, so that the test actually does what its name implies.		2025-07-24 13:09:49 +02:00
..
ans.py	Account for idle timeouts in the "dispatch" test	2025-07-24 13:09:49 +02:00