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:
2
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

Discovered this issue while investigating ~~SERVER-42356~~. It is yet another way for close() to never be called on a FixtureLogger or TestLogger. The changes from https://hg.python.org/cpython/rev/d8802b055474 made it so sched.Event instances returned by sched.scheduler.enter() and sched.scheduler.enterabs() are treated as equal if they have the same (time, priority). It is therefore possible to remove the wrong event from the list when sched.scheduler.cancel() is called.

is related to

SERVER-42356 teardown(finished=True) isn't ever called for the NoOpFixture

Closed

SERVER-32295 Support python 3

Closed

related to

SERVER-72079 Replace our resmoke custom scheduler with python scheduler

Closed

Assignee:: Max Hirschhorn
Reporter:: Max Hirschhorn
Participants:: Githook User, Max Hirschhorn
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Aug 04 2019 06:08:08 AM UTC
Updated:: Oct 29 2023 10:18:23 PM UTC
Resolved:: Aug 06 2019 02:58:38 PM UTC
Confidence Status Last Update:: 04/Aug/19 6:59 AM