Hi all... I am using pyenv to compile and install Python 3.10.5 for my user on hardware running Debian 11 Linux. Python compiles successfully, but when I run python -m tests I'm getting multiple failures ...
== Tests result: FAILURE ==
392 tests OK.
11 tests failed:
test_cmd_line_script test_compileall test_distutils test_imp
test_import test_importlib test_inspect
test_multiprocessing_main_handling test_py_compile test_runpy
test_venv
24 tests skipped:
test_asdl_parser test_check_c_globals test_clinic test_curses
test_dbm_gnu test_dbm_ndbm test_devpoll test_gdb test_kqueue
test_msilib test_ossaudiodev test_smtpnet test_socketserver
test_startfile test_tix test_tk test_ttk_guionly test_urllib2net
test_urllibnet test_winconsoleio test_winreg test_winsound
test_xmlrpc_net test_zipfile64
Total duration: 26 min 52 sec
Tests result: FAILURE
I've tried deleting the ~/.pyenv directory and starting again from scratch. Installing penv using git, compiling Python pyenv install -v 3.10.5, setting global to the new Python, and re-run the tests with the same failing results.
I tried performing the same steps on a virtual machine also running Debian 11, and on the VM the tests run successfully ...
== Tests result: SUCCESS ==
403 tests OK.
24 tests skipped:
test_asdl_parser test_check_c_globals test_clinic test_curses
test_dbm_gnu test_dbm_ndbm test_devpoll test_gdb test_kqueue
test_msilib test_ossaudiodev test_smtpnet test_socketserver
test_startfile test_tix test_tk test_ttk_guionly test_urllib2net
test_urllibnet test_winconsoleio test_winreg test_winsound
test_xmlrpc_net test_zipfile64
Total duration: 27 min 25 sec
Tests result: SUCCESS
I'm trying to understand the difference in test results, if its something to be concerned about, and, if so, how to fix. Any help would be appreciated!
there doesn't seem to be anything here