mirror of
https://github.com/storytold/vectorcraft.git
synced 2026-10-29 12:17:14 -06:00
dotCooCoo
e02b43b6be
The vectorcraft-mcp tests of the remote backend in tests.rs gave a fake app 2 or 5 s to accept a connection or to read a request, and waited 2 s for a connection to end or a line to arrive. When a busy machine held the client's thread for longer, the fake app gave up and the test failed. These waits now use WAIT (20 s). remote_connect_fails_fast asserted that a refused connect returned within 5 s, and remote_call_reports_nothing_sent_when_reconnect_is_refused asserted that the call returned within 2 s. On Windows a refused local connect ends at the backend's own 800 ms connect timeout. A connect without that timeout takes about 2 s. The 5 s bound did not tell the two apart, and the 2 s bound left 1.2 s for any pause of the thread. Both tests now bound the connect by FAILED_CONNECT (1.5 s) and run it up to five times, until one run is under the bound. The second test checks the error of every run.