while testing my build of cpython it hangs on test 198/404 and will not continue unless interrupted with ctrl-C.

the build is fairly sound, but I can't test anything after test 198/404 cause it gets stuck.

What is your OS? A Linux on bare metal? Or a container? What are versions of Linux kernel, libc and C compiler? Or more generally the name and verison of your Linux distro?

There are many errors:

* test_fcntl failed
* test_import failed
* test_epoll failed

Can you please run only these tests in verbose mode, and attach the output?

Example:

./python -m test -v test_fcntl test_import test_epolls

my OS is Ubuntu on Windows 10
<https://msdn.microsoft.com/en-us/commandline/wsl/about>. The new Linux
subsystem for Windows 10
Linux version 3.4.0-Microsoft (Microsoft@Microsoft.com) (gcc version 4.7
(GCC) ) #1 SMP PREEMPT Wed Dec 31 14:42:53 PST 2014

Distributor ID: Ubuntu
Description:    Ubuntu 14.04.5 LTS
Release:        14.04
Codename:       trusty

ldd (Ubuntu EGLIBC 2.19-0ubuntu6.9) 2.19

Windows 10 is running on bare metal.
I have included a log file with the results from the test.

On Thu, Dec 8, 2016 at 8:55 PM, STINNER Victor <report@bugs.python.org>
wrote:

>
> STINNER Victor added the comment:
>
> What is your OS? A Linux on bare metal? Or a container? What are versions
> of Linux kernel, libc and C compiler? Or more generally the name and
> verison of your Linux distro?
>
> There are many errors:
>
> * test_fcntl failed
> * test_import failed
> * test_epoll failed
>
> Can you please run only these tests in verbose mode, and attach the output?
>
> Example:
>
> ./python -m test -v test_fcntl test_import test_epolls
>
> ----------
> nosy: +haypo
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue28874>
> _______________________________________
>

Extract of cpython-testlogging.log:

0:08:58 [198/404] test_logging
--- Logging error ---
Traceback (most recent call last):
  File "/mnt/d/Share/source/cpython-master/Lib/logging/handlers.py", line 634, in emit
    self.send(s)
  File "/mnt/d/Share/source/cpython-master/Lib/logging/handlers.py", line 692, in send
    self.sock.sendto(s, self.address)
OSError: [Errno 22] Invalid argument
Call stack:
  File "/mnt/d/Share/source/cpython-master/Lib/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/mnt/d/Share/source/cpython-master/Lib/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/mnt/d/Share/source/cpython-master/Lib/test/regrtest.py", line 50, in <module>
    _main()
  File "/mnt/d/Share/source/cpython-master/Lib/test/regrtest.py", line 46, in _main
    main()
  File "/mnt/d/Share/source/cpython-master/Lib/test/libregrtest/main.py", line 532, in main
    Regrtest().main(tests=tests, **kwargs)
  File "/mnt/d/Share/source/cpython-master/Lib/test/libregrtest/main.py", line 468, in main
    self._main(tests, kwargs)
  File "/mnt/d/Share/source/cpython-master/Lib/test/libregrtest/main.py", line 490, in _main
    self.run_tests()
  File "/mnt/d/Share/source/cpython-master/Lib/test/libregrtest/main.py", line 418, in run_tests
    self.run_tests_sequential()
  File "/mnt/d/Share/source/cpython-master/Lib/test/libregrtest/main.py", line 343, in run_tests_sequential
    result = runtest(self.ns, test)
  File "/mnt/d/Share/source/cpython-master/Lib/test/libregrtest/runtest.py", line 129, in runtest
    result = runtest_inner(ns, test, display_failure=not ns.verbose)
  File "/mnt/d/Share/source/cpython-master/Lib/test/libregrtest/runtest.py", line 165, in runtest_inner
    test_runner()
  File "/mnt/d/Share/source/cpython-master/Lib/test/support/__init__.py", line 1576, in inner
    return func(*args, **kwds)
  File "/mnt/d/Share/source/cpython-master/Lib/test/test_logging.py", line 4334, in test_main
    support.run_unittest(*tests)
  File "/mnt/d/Share/source/cpython-master/Lib/test/support/__init__.py", line 1909, in run_unittest
    _run_suite(suite)
  File "/mnt/d/Share/source/cpython-master/Lib/test/support/__init__.py", line 1875, in _run_suite
    result = runner.run(suite)
  File "/mnt/d/Share/source/cpython-master/Lib/test/support/__init__.py", line 1751, in run
    test(result)
  File "/mnt/d/Share/source/cpython-master/Lib/unittest/suite.py", line 84, in __call__
    return self.run(*args, **kwds)
  File "/mnt/d/Share/source/cpython-master/Lib/unittest/suite.py", line 122, in run
    test(result)
  File "/mnt/d/Share/source/cpython-master/Lib/unittest/suite.py", line 84, in __call__
    return self.run(*args, **kwds)
  File "/mnt/d/Share/source/cpython-master/Lib/unittest/suite.py", line 122, in run
    test(result)
  File "/mnt/d/Share/source/cpython-master/Lib/unittest/case.py", line 649, in __call__
    return self.run(*args, **kwds)
  File "/mnt/d/Share/source/cpython-master/Lib/unittest/case.py", line 601, in run
    testMethod()
  File "/mnt/d/Share/source/cpython-master/Lib/test/test_logging.py", line 1580, in test_output
    logger.error("spam")
Message: 'spam'
Arguments: ()
^C
Test suite interrupted by signal SIGINT.


I'm watching closely Windows buildbots for 2 years, and I don't recall having seen this error recently. So I close the issue as "out of date".

I am observing this issue while building 3.6.8 version on CentOS 7.6. Shall we reopen the bug? Thanks, Yury.

And same happens to me when building version 3.7.3.
I'm building with gcc (GCC) 4.8.5.

I'm facing similar issue with test_logging in python3.5.2-2ubuntu0~16.04.12. Test just get hangs and so, our builders kill the build process without a successful ending.

[1/1] test_locale
1 test OK.
[1/1] test_logging
E: Build killed with signal TERM after 150 minutes of inactivity

Could someone provide any info in how to handle with this issue? Also, reopen this issue, if possible. 
It's affecting our 3.4 and 3.5 pythons.

Thanks!

Python 3.5 is no longer supported (no bugfix, no security fix). This issue is closed.

I was seeing this problem when building 3.6.4. Fixed it by replacing the test cert with a newer one from 3.6.13:

    curl https://raw.githubusercontent.com/python/cpython/v3.6.13/Lib/test/keycert.pem > ./Lib/test/keycert.pem

Hope this helps someone else one day..

And the day came...
Thank you very much wim.glenn

I had this issue when building python 3.6.4

messages: + msg378243
versions: + Python 3.5, - Python 3.7

stage: resolved

messages: + msg283003