GeezerVison

Triggering the buildbots to get logs with the new message.

🤖 New build scheduled with the buildbot fleet by @arhadthedev for commit bf3c063 🤖

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

The tests are done:

======================================================================
FAIL: test_activate_shell_script_has_no_dos_newlines (test.test_venv.BasicTest.test_activate_shell_script_has_no_dos_newlines)
Test that the `activate` shell script contains no CR LF.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "D:\buildarea\pull_request.bolen-windows10\build\Lib\test\test_venv.py", line 628, in test_activate_shell_script_has_no_dos_newlines
    self.assertFalse(line.endswith(b'\r\n'), error_message)
AssertionError: True is not false : CR LF found in line 1
----------------------------------------------------------------------

According to https://git-scm.com/docs/gitattributes#_text, we need to check if core.autocrlf is set in git config on Windows because it overrides .gitattributes.

It only overrides the value of core.eol being used as the default, which is not what is happening here. We've explicitly set the line ending for the file, we just need anyone who's checked it out in the past to delete it and check it out again (tested on my own Windows machine, which has core.autocrlf set).

If we can't find a way to force the buildbots to do a clean checkout, instead of reusing their existing one, then we probably need to ping all the owners to log in and do it manually.

The buildbot results look good (the expected failure), so merging this. Buildbot discussion back to #103088 please.