-
Type: Task
-
Resolution: Fixed
-
Priority: Unknown
-
Affects Version/s: None
-
Component/s: None
Description
Using TRACE_SOCKETS=true we can see that the "Network error on Monitor check " test leaves a socket open after the test completes. (see socket 00219).
✔ Network error on Monitor check (1121ms) ⚡︎ socket 00204 not destroyed [127.0.0.1:60164 → 127.0.0.1:31001] ⚡︎ socket 00219 not destroyed [127.0.0.1:60179 → 127.0.0.1:31001] hello-timeout ✔ Network timeout on Monitor handshake (1412ms) ⚡︎ socket 00219 not destroyed [127.0.0.1:60179 → 127.0.0.1:31001] ⚡︎ socket 00226 not destroyed [127.0.0.1:60186 → 127.0.0.1:31001] ✔ Network timeout on Monitor check (2020ms) ⚡︎ socket 00219 not destroyed [127.0.0.1:60179 → 127.0.0.1:31001] ⚡︎ socket 00247 not destroyed [127.0.0.1:60207 → 127.0.0.1:31001] ✔ Driver extends timeout while streaming (2017ms)
AC
- skip test for now
- is cloned by
-
NODE-4573 Fix leak and unskip Network error on Monitor check from hello-network-error.json
- Backlog