[Thomas Wouters]
> ...
> One remaining issue with refleakhunting on my machine is that test_tcl can't
> stand being run twice. Even without -R, this makes Python hang while waiting
> for a mutex in the second run through test_tcl:
>
> ...trunk $ ./python -E -tt Lib/test/regrtest test_tcl test_tcl
>
[Thomas Wouters]
>> test_threading_local is not entirely consistent, but it looks a lot more
>> reliable on my box than on Neal's automated mails:
>>
>> test_threading_local
>> beginning 11 repetitions
>> 12345678901
>> ...
>> test_threading_local leaked [34, 34, 34, 34, 34, 26, 26, 22, 34]
On 4/16/06, Thomas Wouters <[EMAIL PROTECTED]> wrote:
test_threading_local is not entirely consistent, but it looks a lot more reliable on my box than on Neal's automated mails:test_threading_localbeginning 11 repetitions12345678901
...
test_threading_local leaked [34, 34, 34, 34, 34, 26, 2
On my box, the latest batch of refleak fixes seems to have fixed all but one of the leaky tests. test_threading_local still leaks, but it leaks rather consistently now (which is new.) I'm not able to make the other ones leak with any combination of '-u' or removing .pyc's beforehand or running long
