gh-103053: Run tools test_freeze on buildbot

[vstinner]

No longer skip test_tools.test_freeze on buildbots.

• Issue: test_tools: test_freeze_simple_script() times out after 15 min: --with-lto --enable-optimizations (s390x LTO buildbots) #103053

[bedevere-bot]

🤖 New build scheduled with the buildbot fleet by @vstinner for commit ff148fe 🤖

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

[vstinner]

Oh, test_tools fails on FreeBSD: https://buildbot.python.org/all/#/builders/1228/builds/8

--- pybuilddir.txt ---
./python -E -S -m sysconfig --generate-posix-vars ; if test $? -ne 0 ; then echo "generate-posix-vars failed" ; rm -f ./pybuilddir.txt ; exit 1 ; fi
sh: ./python: not found
*** [pybuilddir.txt] Error code 127

[vstinner]

!buildbot AMD64 FreeBSD PR

[vstinner]

Windows x64 failed: issue gh-109878:

FAIL: test_wait_for_timeout_less_then_0_or_0 (test.test_asyncio.test_waitfor.AsyncioWaitForTest.test_wait_for_timeout_less_then_0_or_0) (timeout=-1)
----------------------------------------------------------------------
Traceback (most recent call last):
File "D:\a\cpython\cpython\Lib\test\test_asyncio\test_waitfor.py", line 124, in test_wait_for_timeout_less_then_0_or_0
self.assertLess(t1 - t0, 0.1)
AssertionError: 0.10999999999989996 not less than 0.1

[bedevere-bot]

🤖 New build scheduled with the buildbot fleet by @vstinner for commit da55dc2 🤖

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

[vstinner]

!buildbot AMD64 FreeBSD PR

[vstinner]

!buildbot AMD64 FreeBSD PR

[vstinner]

!buildbot AMD64 FreeBSD PR

[bedevere-bot]

🤖 New build scheduled with the buildbot fleet by @vstinner for commit 742381c 🤖

The command will test the builders whose names match following regular expression: AMD64 FreeBSD PR

The builders matched are:

• AMD64 FreeBSD PR

[vstinner]

!buildbot AMD64 FreeBSD PR

[bedevere-bot]

🤖 New build scheduled with the buildbot fleet by @vstinner for commit 13eee42 🤖

The command will test the builders whose names match following regular expression: AMD64 FreeBSD PR

The builders matched are:

• AMD64 FreeBSD PR

[vstinner]

!buildbot AMD64 FreeBSD PR

[bedevere-bot]

🤖 New build scheduled with the buildbot fleet by @vstinner for commit 39424ce 🤖

The command will test the builders whose names match following regular expression: AMD64 FreeBSD PR

The builders matched are:

• AMD64 FreeBSD PR

[vstinner]

Oh, test_tools fails on FreeBSD

The problem is this code in Makefile.pre.in:

$(BUILDPYTHON):	Programs/python.o $(LINK_PYTHON_DEPS)
$(LINKCC) $(PY_CORE_LDFLAGS) $(LINKFORSHARED) -o $@ Programs/python.o $(LINK_PYTHON_OBJS) $(LIBS) $(MODLIBS) $(SYSLIBS)

On the buildbot, we have:

• $(BUILDPYTHON) = python
• $@ = /tmp/test_python_7mxk6_9f/tmpxcjgcgeh/cpython/python

The problem is that /tmp/test_python_7mxk6_9f/tmpxcjgcgeh/cpython is the source directory, not the build directory: /tmp/test_python_7mxk6_9f/tmpxcjgcgeh/python-build.

I'm not sure why FreeBSD make creates an absolute path to the source directory, instead of the build directory.

For me, $(BUILDPYTHON) = python is the correct behavior. The question is more to know how to generate a gcc -o value which is in the right directory.

Note: on my FreeBSD 13 VM, I don't get this behavior when I build Python out of tree. It works the same as Linux make: $@ is just python.

[vstinner]

!buildbot AMD64 FreeBSD PR

[bedevere-bot]

🤖 New build scheduled with the buildbot fleet by @vstinner for commit 32d95c9 🤖

The command will test the builders whose names match following regular expression: AMD64 FreeBSD PR

The builders matched are:

• AMD64 FreeBSD PR

[vstinner]

!buildbot AMD64 FreeBSD PR

[bedevere-bot]

🤖 New build scheduled with the buildbot fleet by @vstinner for commit 32d95c9 🤖

The command will test the builders whose names match following regular expression: AMD64 FreeBSD PR

The builders matched are:

• AMD64 FreeBSD PR

[vstinner]

I wrote real fixes: PR #110451 and PR #110449.