classification
Title: test_logging report reference leak
Type: Stage:
Components: Versions:
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: vinay.sajip, xiang.zhang
Priority: normal Keywords:

Created on 2017-04-20 11:03 by xiang.zhang, last changed 2017-04-21 10:20 by vinay.sajip.

Messages (3)
msg291961 - (view) Author: Xiang Zhang (xiang.zhang) * (Python committer) Date: 2017-04-20 11:03
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.
msg291986 - (view) Author: Vinay Sajip (vinay.sajip) * (Python committer) Date: 2017-04-20 17:16
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", "credits" or "license" for more information.
>>>
$ ./python -m test.regrtest -R : test_logging
Run tests sequentially
0:00:00 [1/1] test_logging
beginning 9 repetitions
123456789
.........
test_logging passed in 3 min 2 sec
1 test OK.

Total duration: 3 min 2 sec
Tests result: SUCCESS

I do sometimes get errors if I run again, e.g.

test_logging leaked [-164, 164, 0, 0] references, sum=0
test_logging leaked [-29, 31, 0, 0] memory blocks, sum=2

but results appear different every time, it seems. Is there any way to get them reproducibly?
msg292023 - (view) Author: Vinay Sajip (vinay.sajip) * (Python committer) Date: 2017-04-21 10:20
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
test_logging leaked [-54, 56, -54, 2] memory blocks, sum=-50
test_logging failed in 2 min 57 sec

How can you be sure the problem is here rather than in the reference leak checks?
History
Date User Action Args
2017-04-21 10:20:46vinay.sajipsetmessages: + msg292023
2017-04-20 17:16:10vinay.sajipsetmessages: + msg291986
2017-04-20 11:03:04xiang.zhangcreate