-
Type:
Task
-
Resolution: Done
-
Priority:
Unknown
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
None
-
Python Drivers
-
None
-
None
-
None
-
None
-
None
-
None
Context
test_close_closes_sockets can be flaky due to test not waiting for monitor threads/tasks to close before asserting.
Definition of done
Make the test wait until monitor threads/tasks complete.
Pitfalls
What should the implementer watch out for? What are the risks?