Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.2.1, 4.3.1
Affects Version/s: None
Component/s: Testing Infrastructure
Labels:
- tig-resmoke

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v4.2
Sprint:
STM 2019-08-12
Linked BF Score:
31
Story Points:
1
Confidence Status:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
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

Assignee:: Max Hirschhorn

Reporter:: Robert Guo (Inactive)

Participants:: Githook User, Max Hirschhorn, Robert Guo

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: Jul 23 2019 06:31:55 PM UTC

Updated:: Oct 29 2023 10:18:52 PM UTC

Resolved:: Aug 06 2019 02:58:56 PM UTC

Confidence Status Last Update:: 04/Aug/19 6:59 AM