-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: Testing
-
Not Needed
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
- unskip test
- identify why a socket begins to leak and ensure it is closed
- It possibly relates to how the runner cleans up resources
Follow up
- This can be closed as won't do if the test works in the migration to the unified runner
