🤖 New build scheduled with the buildbot fleet by@erlend-aasland for commita02e90a 🤖

If you want to schedule another build, you need to add the:hammer: test-with-refleak-buildbots label again.

@kumaraditya303: we're failingtest_finalize_structseq oftest_embed. the type version contract is invalidated¹ and thePy_TPFLAGS_VALID_VERSION_TAG assert in_PyType_Lookup is triggered here:

AFAICS, the contract betweentp_version_tag andPy_TPFLAGS_VALID_VERSION_TAG seems to hold all across the APIs² implemented typeobject.c, and from what I can see, the runtime uses only these APIs to mess with the type version.

Any ideas?

Hmm, debugging shows that it issys.int_info for which it is failing, this PR has nothing to with that so I guess it is a runtime bug somewhere.

Note for self:

Loop #2 ---\nobject address  : 0x5633734aa7e0\nobject refcount : 30\nobject type     : 0x563373352ce0\nobject type name: type\nobject repr     : <class 'sys.int_info'>\n_testembed: Objects/typeobject.c:4176: _PyType_Lookup: Assertion `_PyType_HasFeature(type, Py_TPFLAGS_VALID_VERSION_TAG)'

Hmm, debugging shows that it issys.int_info for which it is failing, this PR has nothing to with that so I guess it is a runtime bug somewhere.

Hm, but it does not fail onmain; it only fails with this patch applied. I've tried (locally) to pull in latestmain, just to be sure.

FTR, Kumar found the culprit. See#101696.

Thanks, Kumar! Let's land.