Python 3.11.0a6 is blocked
Hi everyone,
Unfortunately, we have some issues marked as release blockers that are holding the 3.11.0a6 release. Some of these issues have been solved but we still have a couple of them. Hopefully, we will solve these soon and I will proceed with the release.
Thanks for your understanding.
Regards from sunny Salamanca, Pablo Galindo Salgado
Hi everyone,
Unfortunately, the release of 3.11.0a6 is still blocked because all reflect buildbots are failing:
https://buildbot.python.org/all/#/release_status
I will try to identify the commit(s) that introduced the regression and revert them, but for the time being the release is on hold, sadly.
Regards from rainy Salamanca, Pablo Galindo Salgado
On Wed, 2 Mar 2022 at 14:52, Pablo Galindo Salgado <pablogsal@gmail.com> wrote:
Hi everyone,
Unfortunately, we have some issues marked as release blockers that are holding the 3.11.0a6 release. Some of these issues have been solved but we still have a couple of them. Hopefully, we will solve these soon and I will proceed with the release.
Thanks for your understanding.
Regards from sunny Salamanca, Pablo Galindo Salgado
Update: Seems that the refleaks have been fixed by Inada-san in this commit:
https://github.com/python/cpython/commit/3241cba4ec55ef0b9e73bf7a5a77ef29ae4...
I will wait until the buildbots are green and then try to proceed with the release.
Thanks!
On Thu, 3 Mar 2022 at 20:14, Pablo Galindo Salgado <pablogsal@gmail.com> wrote:
Hi everyone,
Unfortunately, the release of 3.11.0a6 is still blocked because all reflect buildbots are failing:
https://buildbot.python.org/all/#/release_status
I will try to identify the commit(s) that introduced the regression and revert them, but for the time being the release is on hold, sadly.
Regards from rainy Salamanca, Pablo Galindo Salgado
On Wed, 2 Mar 2022 at 14:52, Pablo Galindo Salgado <pablogsal@gmail.com> wrote:
Hi everyone,
Unfortunately, we have some issues marked as release blockers that are holding the 3.11.0a6 release. Some of these issues have been solved but we still have a couple of them. Hopefully, we will solve these soon and I will proceed with the release.
Thanks for your understanding.
Regards from sunny Salamanca, Pablo Galindo Salgado
By the way, AMD64 Arch Linux Usan 3.x started failing because I enabled more tests on this buildbot yesterday.
Previously, "test_faulthandler test_hashlib test_concurrent_futures test_ctypes" were simply skipped on this UBSAN buildbot.
I'm working on fixing the 3 failing tests: test_ctypes, test_faulthandler and test_hashlib https://bugs.python.org/issue46913
So it's not a regression, it's just that the buildbot became stricter.
Victor
participants (2)
-
Pablo Galindo Salgado -
Victor Stinner