diff options
| author | holger krekel <holger@merlinux.eu> | 2011-07-07 21:15:35 +0200 |
|---|---|---|
| committer | holger krekel <holger@merlinux.eu> | 2011-07-07 21:15:35 +0200 |
| commit | c25ea2cbe25795aa76badb11e9cfef87b1120d7f (patch) | |
| tree | 3b20ad89698c1b111e7aefe47dfaebbab9b45a95 /ISSUES.txt | |
| parent | 6a523b4f59a04a061b27e90211c025c5cc0a0485 (diff) | |
| download | pytest-c25ea2cbe25795aa76badb11e9cfef87b1120d7f.tar.gz | |
add a note about hook partial finalization issues
Diffstat (limited to 'ISSUES.txt')
| -rw-r--r-- | ISSUES.txt | 17 |
1 files changed, 10 insertions, 7 deletions
diff --git a/ISSUES.txt b/ISSUES.txt index e39946dcc..7454d37a9 100644 --- a/ISSUES.txt +++ b/ISSUES.txt @@ -7,13 +7,16 @@ tags: bug 2.4 core xdist the protocol now - setup/teardown is called at module level. consider making calling of setup/teardown configurable -profiling / hook call optimization -------------------------------------- -tags: enhancement 2.1 - -bench/bench.py reveals that for very quick running -unit tests the hook architecture is a bit slow. -Profile and improve hook calls. +fix start/finish partial finailization problem +--------------------------------------------------------------- +tags: bug core + +if a configure/runtest_setup/sessionstart/... hook invocation partially +fails the sessionfinishes is not called. Each hook implementation +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 ----------------------------------------- |