Should we also add the three tracemalloc tests to Modules/_testcapi/mem.c?

I think I prefer the "mem" name, but I'm not sure it matters much really. What do you think about including the tracemalloc tests?

I think I prefer the "mem" name, but I'm not sure it matters much really. What do you think about including the tracemalloc tests?

We can add the tracemalloc tests later if we find out they should live in Modules/_testcapi/mem.c

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

Hi! The buildbot wasm32-emscripten node (dynamic linking) 3.x has failed when building commit 00437ad.

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/1056/builds/852) and take a look at the build logs.
4. Check if the failure is related to this commit (00437ad) 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/1056/builds/852

Failed tests:

• test___all__

Failed subtests:

• test_all - test.test___all__.AllTest.test_all

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

== Tests result: FAILURE ==

334 tests OK.

10 slowest tests:

• test_tokenize: 57.6 sec
• test_lib2to3: 44.8 sec
• test_unparse: 41.9 sec
• test_capi: 32.1 sec
• test_argparse: 19.9 sec
• test_statistics: 17.0 sec
• test_unicodedata: 16.2 sec
• test_pickle: 13.2 sec
• test_zipfile: 12.6 sec
• test_decimal: 11.3 sec

1 test failed:
test___all__

98 tests skipped:
test__xxsubinterpreters test_asyncgen test_asyncio
test_check_c_globals test_clinic test_cmd_line
test_concurrent_futures test_contextlib_async test_ctypes
test_curses test_dbm_gnu test_dbm_ndbm test_devpoll test_doctest
test_docxmlrpc test_dtrace test_embed test_epoll test_faulthandler
test_fcntl test_file_eintr test_fork1 test_ftplib test_gdb
test_grp test_httplib test_httpservers test_idle test_imaplib
test_interpreters test_ioctl test_kqueue test_launcher test_lzma
test_mmap test_msilib test_multiprocessing_fork
test_multiprocessing_forkserver test_multiprocessing_main_handling
test_multiprocessing_spawn test_nis test_openpty test_ossaudiodev
test_pdb test_peg_generator test_perf_profiler test_poll
test_poplib test_pty test_pwd test_queue test_readline
test_regrtest test_repl test_resource test_select test_selectors
test_smtplib test_smtpnet test_socket test_socketserver test_spwd
test_ssl test_stable_abi_ctypes test_startfile test_subprocess
test_sys_settrace test_syslog test_tcl test_telnetlib test_thread
test_threadedtempfile test_threading test_threading_local test_tix
test_tkinter test_tools test_ttk test_ttk_textonly test_turtle
test_urllib2 test_urllib2_localnet test_urllib2net test_urllibnet
test_venv test_wait3 test_wait4 test_webbrowser test_winconsoleio
test_winreg test_winsound test_wmi test_wsgiref test_xmlrpc
test_xmlrpc_net test_zipfile64 test_zipimport_support
test_zoneinfo
0:19:49 load avg: 12.38
0:19:49 load avg: 12.38 Re-running failed tests is not supported with --python host runner option.

Total duration: 19 min 49 sec

@erlend-aasland can you please review my fix of this failure? It happens for each PR right now :(

Link: #99519

What do you think about including the tracemalloc tests?

Yep, it makes sense to move them in mem.c.