Ticket #1334 enhancement new

Opened 8 years ago

Last modified 8 years ago

Custom Trial reactor to track resources and handle cleanup

Reported by: jml Owned by:
Priority: normal Milestone:
Component: trial Keywords:
Cc: glyph, radix, exarkun, spiv, itamarst, warner, jml, jknight Branch:
Author: Launchpad Bug:

Description


Change History

1

Changed 8 years ago by jml

Suggestion:
Trial implements a reactor.  All Trial's reactor implementation does is wrap a
real reactor (whichever is specified).  All calls into the reactor are noted and
tracked.  When a test method is finished, any event sources it created but did
not clean up are marked as errors and cleaned up.  When a test class is
finished, any event sources its setUpClass created but did not clean up are
marked as errors and cleaned up.  Anything that is trial internal (say, a
connection to a remote observer used by the reporter) can be ignored safely, and
object lifetimes can be discovered correctly.

This is not a silver bullet.  It will be tedious to implement.  There are cases
it will not automatically handle and will need to be assisted with.  I think a
few simple heuristics can cover most circumstances, but trial may also need an
annotation API to explicitly delineate certain edge cases.

2

Changed 8 years ago by jml

Fixing this would fix #343

3

Changed 8 years ago by jml

Would fix #1304 also

4

Changed 8 years ago by jml

  • owner set to jml

5

Changed 3 years ago by <automation>

  • owner jml deleted
Note: See TracTickets for help on using tickets.