This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vinay.sajip
Recipients vinay.sajip, xiang.zhang
Date 2017-04-20.17:16:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1492708570.17.0.454273492441.issue30115@psf.upfronthosting.co.za>
In-reply-to
Content
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?
History
Date User Action Args
2017-04-20 17:16:10vinay.sajipsetrecipients: + vinay.sajip, xiang.zhang
2017-04-20 17:16:10vinay.sajipsetmessageid: <1492708570.17.0.454273492441.issue30115@psf.upfronthosting.co.za>
2017-04-20 17:16:10vinay.sajiplinkissue30115 messages
2017-04-20 17:16:10vinay.sajipcreate