[issue9815] test_tarfile sometimes ends with error "Cannot remove dir"

Antoine Pitrou added the comment: Adding Michael for review of py3k_fix__AssertRaisesContext.patch. -- nosy: +michael.foord ___ Python tracker ___ ___

[issue9815] test_tarfile sometimes ends with error "Cannot remove dir"

Changes by Hirokazu Yamamoto : -- keywords: +needs review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue9815] test_tarfile sometimes ends with error "Cannot remove dir"

Hirokazu Yamamoto added the comment: Here is the simple test case to demonstrate this issue. -- Added file: http://bugs.python.org/file18897/test_traceback_freed.py ___ Python tracker __

[issue9815] test_tarfile sometimes ends with error "Cannot remove dir"

Antoine Pitrou added the comment: You shouldn't use DEBUG_LEAK except for debugging purposes :) As the doc mentions: “To debug a leaking program call gc.set_debug(gc.DEBUG_LEAK). Notice that this includes gc.DEBUG_SAVEALL, causing garbage-collected objects to be saved in gc.garbage for inspec

[issue9815] test_tarfile sometimes ends with error "Cannot remove dir"

Hirokazu Yamamoto added the comment: Here is the patch to fix this issue. (Please forget first patch) E:\python-dev>py3k -m test.regrtest test_tarfile [1/1] test_tarfile 1 test OK. [85902 refs] E:\python-dev>py3k test_assert_raises.py -- [('foo 2',), None, RuntimeError(

[issue9815] test_tarfile sometimes ends with error "Cannot remove dir"

Hirokazu Yamamoto added the comment: The error went away when I commented out following line. Lib/unittest/case.py(133) self.exception = exc_value.with_traceback(None) I found this by brute force I noticed that test_tar_pipe_open_read_error_v2.py starts to fail from r75241. It stor

[issue9815] test_tarfile sometimes ends with error "Cannot remove dir"

Hirokazu Yamamoto added the comment: I tried test_tar_pipe_open_read_error_v2.py on py3k, I saw 3 uncollectable objects are reported. But they are *collected* by gc.collect() without gc.set_debug(gc.DEBUG_LEAK). (I'm not familiar to gc, so maybe this is normal) I didn't see uncollectable object

[issue9815] test_tarfile sometimes ends with error "Cannot remove dir"

Éric Araujo added the comment: I think the tests should go into 2.7 and 3.1 even if they don’t have the bug. Adding Antoine to nosy, since he’s listed for gc in Misc/maintainers.rst. -- nosy: +pitrou ___ Python tracker

[issue9815] test_tarfile sometimes ends with error "Cannot remove dir"

Hirokazu Yamamoto added the comment: I created separate small test case to reproduce, and I tried it on Python2.7, I couldn't reproduce the issue. And tried it on Python3.1, I couldn't there neither. (Sorry about that... I included 3.1 in version box) And exception might not be related. Because

[issue9815] test_tarfile sometimes ends with error "Cannot remove dir"

Éric Araujo added the comment: Just to be sure: Have you checked this bug doesn’t apply to 2.7? Can you add a regression test? -- nosy: +eric.araujo title: test_tarfile sometimes ends with error "Cannot remoe dir" -> test_tarfile sometimes ends with error "Cannot remove dir" ___