[issue45444] test.test_concurrent_futures fail in x86_ 64 architecture

2022-01-17 Thread STINNER Victor
Change by STINNER Victor : -- nosy: -vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45444] test.test_concurrent_futures fail in x86_ 64 architecture

2022-01-16 Thread Irit Katriel
Change by Irit Katriel : -- versions: -Python 3.7, Python 3.8, Python 3.9 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue45444] test.test_concurrent_futures fail in x86_ 64 architecture

2021-11-02 Thread Hai Shi
Hai Shi added the comment: > I use the Linux operating system (openeuler), kernel version 4.19.90, GCC > version 7.3.0. I directly run the following statement in the virtual machine Hm. I haven't openeuler system, but I get docker container of the euler system. The tests have passed in my

[issue45444] test.test_concurrent_futures fail in x86_ 64 architecture

2021-10-15 Thread tongxiaoge
tongxiaoge added the comment: I compared the log and found that test_socket.HAVE_SOCKET_QIPCRTR is false in x86_ 64, and the value is true in the build log on the aarch64 architecture. I don't know whether it is related to this value. -- Added file:

[issue45444] test.test_concurrent_futures fail in x86_ 64 architecture

2021-10-15 Thread tongxiaoge
tongxiaoge added the comment: I use the Linux operating system (openeuler), kernel version 4.19.90, GCC version 7.3.0. I directly run the following statement in the virtual machine: 1、python3 Lib/test/test_concurrent_futures.py 2、python3 -m test test_concurrent_futures The test cases are

[issue45444] test.test_concurrent_futures fail in x86_ 64 architecture

2021-10-15 Thread STINNER Victor
STINNER Victor added the comment: What is your operating system? (name/version) Did you try to build Python manually and run the test manually? How did you build Python? What are the configure flags and compiler flags? -- nosy: +vstinner ___

[issue45444] test.test_concurrent_futures fail in x86_ 64 architecture

2021-10-13 Thread tongxiaoge
tongxiaoge added the comment: I reproduced the same problem in Python 3-3.11.0a1 and increased two failure test cases: test_ exceptions and test_ Tools, detailed log is as follows: [ 1937s] 0:27:53 load avg: 5.11 running: test_capi (27 min 51 sec) [ 1966s] 0:28:23 load avg: 5.03 [423/423/3]