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

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

CI cannot find merge base, and decides that this is not worthy running the tests. Buildbots seem to ignore this fact though, so I guess that it's fine if they are green.

UPDATE: a little bit too fast there; AMD64 FreeBSD Non-Debug is green, but it did not run. It failed before even compiling.

This buildbot run does not look good. Do you experience this often on the 3.7 branch, @ambv?

I think it is related to 4ac923f

See also GH-21806

I think backporting both GH-24004 and GH-21806 will fix it. Maybe not both are required, but I think both should be backported.

I think backporting both GH-24004 and GH-21806 will fix it. Maybe not both are required, but I think both should be backported.

Seems reasonable. I triggered #92341 and #92342, but I am not authorized to merge to the 3.7 branch.

Great! I'll pull in 3.7 when the backports land.

The 3.7 branch no longer accept bugfixes, only security fixes: https://devguide.python.org/#status-of-python-branches

Do you consider that this change fix a security issue?

Do you consider that this change fix a security issue?

Yes, see discussion here.