Jarred Sumner 33fac76763 Delete flaky test that made incorrect assumptions about the event loop ...

We cannot assume that the next event loop cycle will yield the expected outcome from the operating system. We can assume certain things happen in a certain order, but when timers run next does not mean kqueue/epoll/iocp will always have the data available there.

2025-07-14 23:58:37 -07:00

..

connect-returns-socket-unix.js

run prettier and add back format action (#13722)

2024-09-03 21:32:52 -07:00

connect-returns-socket.js

add some connect test and type changes (#3013)

2023-05-22 19:48:07 -07:00

echo.js

happy eyeballs (#11206)

2024-05-20 22:12:14 -07:00

keep-event-loop-alive.js

fix(windows) socket and timers/performance tests (#9651)

2024-03-27 10:31:12 -07:00

socket-huge-fixture.js

fix(windows) socket and timers/performance tests (#9651)

2024-03-27 10:31:12 -07:00

socket-leak-fixture.js

run prettier and add back format action (#13722)

2024-09-03 21:32:52 -07:00

socket.test.ts

Use ReadableStream.prototype.* in tests instead of new Response(...).* (#20937)

2025-07-14 00:47:53 -07:00

tcp-server.test.ts

run prettier and add back format action (#13722)

2024-09-03 21:32:52 -07:00