⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot ARM Raspbian 3.x has failed when building commit 447d061.

What do you need to do:

1. Don't panic.
2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
3. Go to the page of the buildbot that failed (https://buildbot.python.org/all/#builders/424/builds/3216) and take a look at the build logs.
4. Check if the failure is related to this commit (447d061) or if it is a false positive.
5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/all/#builders/424/builds/3216

Summary of the results of the build (if available):

== Tests result: ENV CHANGED ==

411 tests OK.

10 slowest tests:

• test_largefile: 6 min 32 sec
• test_venv: 4 min 50 sec
• test_asyncio: 3 min 51 sec
• test_multiprocessing_spawn: 3 min 21 sec
• test_concurrent_futures: 3 min 9 sec
• test_multiprocessing_forkserver: 3 min 2 sec
• test_zipfile: 2 min 44 sec
• test_shutil: 2 min 20 sec
• test_tokenize: 2 min 1 sec
• test_gdb: 1 min 45 sec

1 test altered the execution environment:
test_multiprocessing_forkserver

21 tests skipped:
test_check_c_globals test_devpoll test_idle test_ioctl test_kqueue
test_launcher test_msilib test_peg_generator test_perf_profiler
test_startfile test_tcl test_tix test_tkinter test_ttk
test_ttk_textonly test_turtle test_winconsoleio test_winreg
test_winsound test_wmi test_zipfile64

Total duration: 29 min 29 sec

The buildbot failure appears unrelated to this change and highly isolated, so I'm going to assume it's a spurious failure.