[issue30115] test_logging report reference leak

2017-04-26 Thread Xiang Zhang
Xiang Zhang added the comment: Seems in #30131 Victor has solved this. :-) -- nosy: +haypo resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker

[issue30115] test_logging report reference leak

2017-04-21 Thread Vinay Sajip
Vinay Sajip added the comment: Also getting values I'm not sure how to interpret: $ ./python -m test.regrtest -R : test_logging Run tests sequentially 0:00:00 [1/1] test_logging beginning 9 repetitions 123456789 . test_logging leaked [-164, 164, -164, 0] references, sum=-164

[issue30115] test_logging report reference leak

2017-04-20 Thread Vinay Sajip
Vinay Sajip added the comment: I just did a git pull, then: $ make distclean $ ./configure --with-pydebug $ make EXTRA_CFLAGS="-DPy_REF_DEBUG -DPy_TRACE_REFS" $ ./python Python 3.7.0a0 (heads/master:8f5cdfa, Apr 20 2017, 16:41:52) [GCC 5.4.0 20160609] on linux Type "help", "copyright",

[issue30115] test_logging report reference leak

2017-04-20 Thread Xiang Zhang
New submission from Xiang Zhang: 0:00:00 [1/1] test_logging beginning 9 repetitions 123456789 . test_logging leaked [24, -24, 1, 24] memory blocks, sum=25 test_logging failed in 3 min 15 sec 1 test failed: test_logging Seems d61910c598876788c9b4bf0e116370bbfc5a2f85 is responsible.