Irit Katriel added the comment:
3.6 is no longer maintained. Please create a new issue if you are seeing this
problem on a current version (>= 3.9).
--
nosy: +iritkatriel
resolution: -> out of date
stage: test needed -> resolved
status: open -> closed
___
Martin Panter added the comment:
Thanks for the information. That narrows the problem down, but I still don’t
exactly know why it hangs.
A good workaround may be to put a timeout in the “select” call for a second or
so, and if it times out, raise an exception which will fail the test but let
wmayner added the comment:
Output of `./python3 -m unittest -v test.test_readline`:
testHistoryUpdates (test.test_readline.TestHistoryManipulation) ... ok
test_nonascii_history (test.test_readline.TestHistoryManipulation) ... ok
test_write_read_append (test.test_readline.TestHistoryManipulation)
Martin Panter added the comment:
Perhaps if you ran the tests in verbose mode, that could narrow down which test
it hangs at. Also, if you can capture a KeyboardInterrupt stack trace, that may
help. Not sure if it works with your build setup, but maybe you can run
something like
./python -m u
New submission from wmayner:
I'm trying to build Python 3.6.1 from source with the `--enable-optimizations`
configuration option. As I understand it, this entails running and profiling
all the tests for PGO. When `test_readline` is run, it hangs.
OS: Debian 3.16.43-2 (2017-04-30) x86_64 GNU/Li
