Re: [Python-Dev] "make test" routinely fails to terminate
> me> On the 3.7 branch, "make test" routinely fails to terminate. > Antoine> Can you try to rebuild Python? Use "make distclean" if that helps. > Thanks, Antoine. That solved the termination problem. I still have problems > with test_asyncio failing, but I can live with that for now. Final follow-up. I finally got myself a workable, updateable 3.7 branch in my fork. It looks like the asyncio issues are alsy resolved on both 3.7 and master. Skip ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] "make test" routinely fails to terminate
me> On the 3.7 branch, "make test" routinely fails to terminate. Antoine> Can you try to rebuild Python? Use "make distclean" if that helps. Thanks, Antoine. That solved the termination problem. I still have problems with test_asyncio failing, but I can live with that for now. If "make distclean" is required, I suspect there is a missing/incorrect/incomplete Make dependency somewhere. I suppose "make distclean" is cheap enough that I should do it whenever I switch branches. Skip ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] "make test" routinely fails to terminate
On Sat, 19 May 2018 17:41:18 -0500 Skip Montanaro wrote: > On the 3.7 branch, "make test" routinely fails to terminate. (Pretty > vanilla Ubuntu 17.10 running on a Dell Laptop. Nothing esoteric at all) > Lately, it's been one of the multiprocessing tests. After a long while > (~2000 seconds), I kill it, then it complains many times about lack of a > valid_signals attribute in the signal module: Can you try to rebuild Python? Use "make distclean" if that helps. Regards Antoine. ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] "make test" routinely fails to terminate
On the 3.7 branch, "make test" routinely fails to terminate. (Pretty vanilla Ubuntu 17.10 running on a Dell Laptop. Nothing esoteric at all) Lately, it's been one of the multiprocessing tests. After a long while (~2000 seconds), I kill it, then it complains many times about lack of a valid_signals attribute in the signal module: == ERROR: test_remove_signal_handler_error2 (test.test_asyncio.test_unix_events.SelectorEventLoopSignalTests) -- Traceback (most recent call last): File "/home/skip/src/python/cpython/Lib/unittest/mock.py", line 1191, in patched return func(*args, **keywargs) File "/home/skip/src/python/cpython/Lib/test/test_asyncio/test_unix_events.py", line 219, in test_remove_signal_handler_error2 m_signal.valid_signals = signal.valid_signals AttributeError: module 'signal' has no attribute 'valid_signals' -- Ran 1967 tests in 36.058s FAILED (errors=362, skipped=11) test test_asyncio failed /home/skip/src/python/cpython/Lib/asyncio/base_events.py:605: ResourceWarning: unclosed event loop <_UnixSelectorEventLoop running=False closed=False debug=False> source=self) Re-running test 'test_signal' in verbose mode then reruns test_signal in verbose mode. Earlier today, a run succeeded, so I'm guessing a race condition exists in the test system. I recall encountering a similar problem a few weeks ago and discovered this open ticket: https://bugs.python.org/issue33099 Should I expect this as the normal behavior? Skip ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
