You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
test_type_cache fails with --forever argument #113937
Sorry for this - I certainly introduced it. The first issue should be resolvable by skipping tests if we run out of version tags (like what was done in the preexisting test_tp_version_tag_unique). I'm not sure what could be causing the second, though. @Fidget-Spinner if you'd like another set of eyes on this, lmk
@lazorchakp if you'd like to submit a PR to fix it I would be happy to review it as well! For the second case, it's possible that the specialization has not reverted yet. In CPython, code objects are shared across functions (so every time you create a new function, it reuses the same code object, you can dis.dis a closure to see what I mean). So the specialization from a previous iteration could stick around for abit until it de-specializes by running the loop a few times. Because of that, I think it's fine to remove that line.
test_type_cache seems to be failing for pretty much all the refleak buildbots, probably due to this fix. @Fidget-Spinner, please let me know if you need help.
test_type_cache seems to be failing for pretty much all the refleak buildbots, probably due to this fix. @Fidget-Spinner, please let me know if you need help.
Can you share link to the failing buildbot, please? I cannot reproduce it locally
Activity
Eclips4 commentedon Jan 11, 2024
Seems to be introduced in #113558. This PR should be backported to 3.11 and 3.12 (but not backported yet), that's why I'm adding 3.11 & 3.12 labels.
Theoretically it may not be reproducible on 3.11 (maybe some deep internal changes were made) I'll check it when backports will be done.
Eclips4 commentedon Jan 11, 2024
Another error also occurs if we run this test using
-R 3:3:Fidget-Spinner commentedon Jan 11, 2024
Thanks for the report. I'll take a look.
lazorchakp commentedon Jan 11, 2024
Sorry for this - I certainly introduced it. The first issue should be resolvable by skipping tests if we run out of version tags (like what was done in the preexisting
test_tp_version_tag_unique). I'm not sure what could be causing the second, though. @Fidget-Spinner if you'd like another set of eyes on this, lmkFidget-Spinner commentedon Jan 11, 2024
@lazorchakp if you'd like to submit a PR to fix it I would be happy to review it as well! For the second case, it's possible that the specialization has not reverted yet. In CPython, code objects are shared across functions (so every time you create a new function, it reuses the same code object, you can
dis.disa closure to see what I mean). So the specialization from a previous iteration could stick around for abit until it de-specializes by running the loop a few times. Because of that, I think it's fine to remove that line.lazorchakp commentedon Jan 11, 2024
Oh that's interesting! I should be able to get a PR open pretty quickly
pythongh-113937 Fix failures in type cache tests due to re-running
gh-113937 Fix failures in type cache tests due to re-running (GH-113953)
encukou commentedon Jan 12, 2024
test_type_cacheseems to be failing for pretty much all the refleak buildbots, probably due to this fix.@Fidget-Spinner, please let me know if you need help.
Eclips4 commentedon Jan 12, 2024
Can you share link to the failing buildbot, please? I cannot reproduce it locally
encukou commentedon Jan 12, 2024
Oh, I read the wrong timestamp in my buildbot triage :(
Sorry for the alarm!
pythongh-113937 Fix failures in type cache tests due to re-running (p…
pythongh-113937 Fix failures in type cache tests due to re-running (p…
pythongh-113937 Fix failures in type cache tests due to re-running (p…
[3.11] gh-89811: Check for valid tp_version_tag in specializer (GH-11…
pythongh-113937 Fix failures in type cache tests due to re-running (p…
pythongh-113937 Fix failures in type cache tests due to re-running (p…