`test_tracemalloc_track_race` segfault on buildbot

Crash report

Seen on the ARM Raspbian 3.x buildbot, but I suspect it's not Raspbian specific:

https://buildbot.python.org/#/builders/424/builds/12446/steps/6/logs/stdio

0:02:36 load avg: 3.51 [177/497/1] test_tracemalloc worker non-zero exit code (Exit code -11 (SIGSEGV))
test_late_untrack (test.test_tracemalloc.TestCAPI.test_late_untrack) ... ok
test_stop_track (test.test_tracemalloc.TestCAPI.test_stop_track) ... ok
test_stop_untrack (test.test_tracemalloc.TestCAPI.test_stop_untrack) ... ok
test_tracemalloc_track_race (test.test_tracemalloc.TestCAPI.test_tracemalloc_track_race) ... Fatal Python error: Segmentation fault

Thread 0xf4afe400 [python] (most recent call first):

Thread 0xf52ff400 [python] (most recent call first):
  <freed thread state>

<freed thread state>

Current thread's C stack trace (most recent call first):
  <system returned no stack trace>

Extension modules: math.integer, _testcapi, _testinternalcapi (total: 3)

Beginne mit test.test_tracemalloc.TestCAPI.test_tracemalloc_track_race und reproduziere das im Issue verlinkte ARM-Raspbian-Buildbot-Log oder untersuche es. Verfolge den SIGSEGV und bestätige, dass der Test auf der betroffenen Buildbot-Konfiguration ohne Beendigung eines Workers mit einem Exit-Code ungleich null abgeschlossen wird.