Relationships
#4717 start_server_test: the one-interface-address test flakes when a parallel test binds 127.0.0.1 on the same port
Opened by zack · 11/13/2026· Shipped 11/13/2026
integration/start_server_test.ts, test 'startStartServer: on one interface address, serves that address and opens the socket from it with no other trusted names', asserts that rawStatus to 127.0.0.1: rejects while the start server listens only on the routable IPv4 address. Binding : does not reserve 127.0.0.1:, so under the sharded parallel suite another test server can bind loopback on the same port number and the connection succeeds. The assertion then fails with 'AssertionError: Expected function to reject' at start_server_test.ts:2076.
Seen in a verify-build run (shard 3, 1 failed of 9671) on a branch that does not touch the start server. The file passes on its own (55/55).
Expected: the test proves the loopback address is not served without depending on the port being free on loopback, for example by asserting on the response or the connection's peer, rather than on a refused connect.
Shipped
Click a lifecycle step above to view its details.
Sign in to post a ripple.