|
Seems that related to #104020 |
Sorry, something went wrong.
|
🤖 New build scheduled with the buildbot fleet by @AlexWaygood for commit 8dbad09 🤖 If you want to schedule another build, you need to add the 🔨 test-with-refleak-buildbots label again. |
Sorry, something went wrong.
|
Thanks Alex for the buildbots start. But, no one from buildbots use a windows system. |
Sorry, something went wrong.
|
!buildbot Windows.*Refleak |
Sorry, something went wrong.
|
🤖 New build scheduled with the buildbot fleet by @AlexWaygood for commit 8dbad09 🤖 The command will test the builders whose names match following regular expression: Windows.*Refleak The builders matched are: |
Sorry, something went wrong.
|
!buildbot .*Windows.Refleak. |
Sorry, something went wrong.
|
🤖 New build scheduled with the buildbot fleet by @AlexWaygood for commit 8dbad09 🤖 The command will test the builders whose names match following regular expression: .*Windows.*Refleak.* The builders matched are: |
Sorry, something went wrong.
There was a problem hiding this comment.
Please add a Py_tp_clear slot and do the work there. You can call that function from dealloc. Also, the traverse function must be updated similarly.
Sorry, something went wrong.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request. |
Sorry, something went wrong.
|
Also, in dealloc we first untrack from GC, then we clear. |
Sorry, something went wrong.
|
I have made the requested changes; please review again |
Sorry, something went wrong.
|
Thanks for making the requested changes! @erlend-aasland: please review the changes made to this pull request. |
Sorry, something went wrong.
|
I left some more remarks. I'll follow this up tomorrow. |
Sorry, something went wrong.
|
Could you let me know if you've confirmed the error is fixed on Windows? @Eclips4 |
Sorry, something went wrong.
|
Could you let me know if you've confirmed the error is fixed on Windows? @Eclips4 Yeah, refleak are gone: ./python -m test -R 3:3 test_ctypes
Running Debug|x64 interpreter...
0:00:00 Run tests sequentially
0:00:00 [1/1] test_ctypes
beginning 6 repetitions
123456
a=5, b=10, c=15
a=5, b=10, c=15
.a=5, b=10, c=15
a=5, b=10, c=15
.a=5, b=10, c=15
a=5, b=10, c=15
.a=5, b=10, c=15
a=5, b=10, c=15
.a=5, b=10, c=15
a=5, b=10, c=15
.a=5, b=10, c=15
a=5, b=10, c=15
.
test_ctypes passed in 31.2 sec
== Tests result: SUCCESS ==
1 test OK.
Total duration: 31.3 sec
Tests result: SUCCESS
Also, thanks for your help! |
Sorry, something went wrong.
|
Thanks! |
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.