-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
Fully Compatible
-
ALL
-
v4.2
-
STM 2019-08-12
-
31
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The flush thread will block forever for the next event if there isn't one lined up.
We should make it not wait. One way could be to use the non-blocking version of scheduler.run()
- is related to
-
SERVER-28940 Make resmoke fixture setup/teardown their own testcases.
-
- Closed
-
- related to
-
SERVER-42622 resmoke.py doesn't attempt to tear the fixture down if setting it up raises an exception
-
- Closed
-
-
SERVER-42623 sched module in Python 3 causes close() event to mistakenly be canceled, leading to resmoke.py hang
-
- Closed
-