add a note about hook partial finalization issues
This commit is contained in:
parent
6a523b4f59
commit
c25ea2cbe2
15
ISSUES.txt
15
ISSUES.txt
|
@ -7,13 +7,16 @@ tags: bug 2.4 core xdist
|
||||||
the protocol now - setup/teardown is called at module level.
|
the protocol now - setup/teardown is called at module level.
|
||||||
consider making calling of setup/teardown configurable
|
consider making calling of setup/teardown configurable
|
||||||
|
|
||||||
profiling / hook call optimization
|
fix start/finish partial finailization problem
|
||||||
-------------------------------------
|
---------------------------------------------------------------
|
||||||
tags: enhancement 2.1
|
tags: bug core
|
||||||
|
|
||||||
bench/bench.py reveals that for very quick running
|
if a configure/runtest_setup/sessionstart/... hook invocation partially
|
||||||
unit tests the hook architecture is a bit slow.
|
fails the sessionfinishes is not called. Each hook implementation
|
||||||
Profile and improve hook calls.
|
should better be repsonsible for registering a cleanup/finalizer
|
||||||
|
appropriately to avoid this issue. Moreover/Alternatively, we could
|
||||||
|
record which implementations of a hook succeeded and only call their
|
||||||
|
teardown.
|
||||||
|
|
||||||
do early-teardown of test modules
|
do early-teardown of test modules
|
||||||
-----------------------------------------
|
-----------------------------------------
|
||||||
|
|
Loading…
Reference in New Issue