[issue36155] ./python -m test -m test_gc fails

Karthikeyan Singaravelan added the comment: Thanks for the explanation :) -- ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue36155] ./python -m test -m test_gc fails

Pablo Galindo Salgado added the comment: Well, unless there was a bug on the gc, the only way the list l could be on both lists is if in one of them there was something that was saying that is equal to it. To confirm I checked what was equal to l in the second generation and I saw it was moc

[issue36155] ./python -m test -m test_gc fails

Karthikeyan Singaravelan added the comment: No problem. Thanks for fix :) I stumbled upon it due to a typo where I used -m instead of -v in python -m test -m test_gc instead of python -m test -v test_gc . Any suggestion on how you debugged it was mock ? -- _

[issue36155] ./python -m test -m test_gc fails

Pablo Galindo Salgado added the comment: Ok, this one has been fun :) Thanks for finding this one @xtreak! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue36155] ./python -m test -m test_gc fails

Pablo Galindo Salgado added the comment: New changeset d60a79a1015aa26ff7ee3166820ec43558911b60 by Pablo Galindo in branch 'master': bpo-36155: Check for identity on test_gc.test_get_objects (GH-12116) https://github.com/python/cpython/commit/d60a79a1015aa26ff7ee3166820ec43558911b60 ---

[issue36155] ./python -m test -m test_gc fails

Pablo Galindo Salgado added the comment: Yup, I was actually using: ./python.exe -m test test_asyncio test_gc -m test_gc when I found out thst the core cause was mock._ANY :) -- ___ Python tracker __

[issue36155] ./python -m test -m test_gc fails

Karthikeyan Singaravelan added the comment: If I understand this correctly any combination that imports mock._ANY affects test_gc like below combination that uses mock._ANY causes test_gc to fail ? ./python.exe -m unittest unittest.test.testmock test.test_gc [snip output]

[issue36155] ./python -m test -m test_gc fails

Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +12122 stage: -> patch review ___ Python tracker ___ ___ Pytho

[issue36155] ./python -m test -m test_gc fails

Pablo Galindo Salgado added the comment: Ok, this is happening because there is a unittest.mock._ANY in the second generation. -- ___ Python tracker ___ _

[issue36155] ./python -m test -m test_gc fails

Pablo Galindo Salgado added the comment: But this only happens when running the test suite as ./python.exe -m test -m test_gc -- ___ Python tracker ___ __

[issue36155] ./python -m test -m test_gc fails

Pablo Galindo Salgado added the comment: This may be more complicated that it seems as these two statements are true at the same time: l in gc.get_objects(generation=0) True p l in gc.get_objects(generation=2) True -- ___ Python tracker

[issue36155] ./python -m test -m test_gc fails

Pablo Galindo Salgado added the comment: It seems that some collection from some other test is happening between the three calls to get_objects: self.assertIn(l, gc.get_objects(generation=0)) self.assertNotIn(l, gc.get_objects(generation=1)) self.assertNotIn(l, gc.get_objects(generation=2))

[issue36155] ./python -m test -m test_gc fails

New submission from Karthikeyan Singaravelan : I am not sure of the exact cause about this failure but `./python.exe -m test -m test_gc` fails though `./python.exe -m test -v test_gc` passes. This test was recently added with 175421b58cc97a2555e474f479f30a6c5d2250b0 and issue36016. ./python.e