Buildbot updates for Python 3.8

[boomanaiden154]

Landing #78828 (as a part of https://discourse.llvm.org/t/rfc-upgrading-llvms-minimum-required-python-version/67571) caused failures on the following buildbots:

1. sanitizer-pcc64be-linux - emailed
2. libc-x86_64-debian-fullbuild-dbg-asan - @michaelrj-google @lntue @nickdesaulniers
3. clang-ppc64be-linux-test-suite - emailed
4. libc-x86_64-debian-gcc-fullbuild-dbg - @michaelrj-google @lntue @nickdesaulniers
5. polly-arm-linux - emailed
6. clangd-ubuntu-tsan - @ChristianKuehnel
7. sanitizer-x86_64-linux-android - @vitalybuka
8. clang-ppc64le-linux-test-suite - emailed
9. sanitizer-ppc64le-linux - emailed
10. ppc64le-lld-multistage-test - emailed
11. libc-x86_64-debian-dbg-runtimes-build - @michaelrj-google @lntue @nickdesaulniers
12. libc-x86_64-debian - @michaelrj-google @lntue @nickdesaulniers
13. libc-x86_64-debian-dbg-asan - @michaelrj-google @lntue @nickdesaulniers
14. clang-ppc64le-linux-multistage - emailed
15. libc-x86_64-debian-fullbuild-dbg - @michaelrj-google @lntue @nickdesaulniers
16. ppc64le-mlir-rhel-clang - emailed
17. ppc64le-flang-rhel-clang - emailed

These are the buildbots that I saw fail after landing the Python 3.8 upgrade (status page. It's possible there are more failures as I only left the patch in for less than an hour before pulling it, so we'll probably have to do another round of this. I have either pinged buildbot maintainers here or emailed them with a link to this issue so that we can get things moving.

Action needed: Please upgrade the buildbot(s) for which you are a maintainer to Python 3.8 or newer so we can reland the change described in the RFC (and/or add additional context/a timeline on this issue/the discourse RFC thread).

[llvmbot]

@llvm/issue-subscribers-infrastructure

Author: Aiden Grossman (boomanaiden154)

Landing https://github.com//pull/78828 (as a part of https://discourse.llvm.org/t/rfc-upgrading-llvms-minimum-required-python-version/67571) caused failures on the following buildbots: 1. [sanitizer-pcc64be-linux](https://lab.llvm.org/buildbot/#/builders/18/builds/15081) - emailed 2. [libc-x86_64-debian-fullbuild-dbg-asan](https://lab.llvm.org/buildbot/#/builders/162/builds/51187) - @michaelrj-google @lntue @nickdesaulniers 3. [clang-ppc64be-linux-test-suite](https://lab.llvm.org/buildbot/#/builders/231/builds/20820) - emailed 4. [libc-x86_64-debian-gcc-fullbuild-dbg](https://lab.llvm.org/buildbot/#/builders/250/builds/18780) - @michaelrj-google @lntue @nickdesaulniers 5. [polly-arm-linux](https://lab.llvm.org/buildbot/#/builders/56/builds/10516) - emailed 6. [clangd-ubuntu-tsan](https://lab.llvm.org/buildbot/#/builders/131/builds/59442) - @ChristianKuehnel 7. [sanitizer-x86_64-linux-android](https://lab.llvm.org/buildbot/#/builders/77/builds/34771) - @vitalybuka 8. [clang-ppc64le-linux-test-suite](https://lab.llvm.org/buildbot/#/builders/230/builds/25159) - emailed 9. [sanitizer-ppc64le-linux](https://lab.llvm.org/buildbot/#/builders/19/builds/24817) - emailed 10. [ppc64le-lld-multistage-test](https://lab.llvm.org/buildbot/#/builders/36/builds/42792) - emailed 11. [libc-x86_64-debian-dbg-runtimes-build](https://lab.llvm.org/buildbot/#/builders/225/builds/31362) - @michaelrj-google @lntue @nickdesaulniers 12. [libc-x86_64-debian](https://lab.llvm.org/buildbot/#/builders/78/builds/65860) - @michaelrj-google @lntue @nickdesaulniers 13. [libc-x86_64-debian-dbg-asan](https://lab.llvm.org/buildbot/#/builders/73/builds/62872) - @michaelrj-google @lntue @nickdesaulniers 14. [clang-ppc64le-linux-multistage](https://lab.llvm.org/buildbot/#/builders/121/builds/39265) - emailed 15. [libc-x86_64-debian-fullbuild-dbg](https://lab.llvm.org/buildbot/#/builders/163/builds/51774) - @michaelrj-google @lntue @nickdesaulniers 16. [ppc64le-mlir-rhel-clang](https://lab.llvm.org/buildbot/#/builders/88/builds/71503) - emailed 17. [ppc64le-flang-rhel-clang](https://lab.llvm.org/buildbot/#/builders/21/builds/92881) - emailed

These are the buildbots that I saw fail after landing the Python 3.8 upgrade (status page. It's possible there are more failures as I only left the patch in for less than an hour before pulling it, so we'll probably have to do another round of this. I have either pinged buildbot maintainers here or emailed them with a link to this issue so that we can get things moving.

Action needed: Please upgrade the buildbot(s) for which you are a maintainer to Python 3.8 or newer so we can reland the change described in the RFC (and/or add additional context/a timeline on this issue/the discourse RFC thread).

[kadircet]

Issue title says 3.10, but I believe that's a typo and this should be 3.8, right?

[boomanaiden154]

Issue title says 3.10, but I believe that's a typo and this should be 3.8, right?

Good point. Updated to reflect that the minimum version is only being bumped to 3.8.

[nickdesaulniers]

Yesterday I upgraded the libc buildbots from debian 10 to debian 12. They're now running Python 3.11.2.

[vitalybuka]

CC @fmayer

[fmayer]

Running update of the Android buildbot to Ubuntu focal (which has Python 3.8)

[fmayer]

sanitizer-x86_64-linux-android updated:

$ python3 --version
Python 3.8.10

[lei137]

The PowerPC linux LE and BE bots have been updated to use Python 3.8.18.

[DeinAlptraum]

Since all boxes on the list are ticked, is there a reason this is still open?
If not, can we repeat #78828 now?

[boomanaiden154]

Yes. I just realized that someone updated the clangd-ubuntu-tsan bot yesterday. I just need to do the actual push and see if anything else breaks again.

I will probably try and do that today.