New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AIX: test_curses crashes buildbot #87825
Comments
Since bpo-42789 the AIX bot's have crashed - to the extent that the bot's did not even return results. Part of this has been resolved, for now, by using: $ export TERM=unknown
$ buildbot start buildarea However, the test still crash because AIX default libcurses.a does not include support for update_lines_cols(). This patch should allow test_curses.py to pass in the buildbot. When run from command-line as: $ TERM=unknown ./python Lib/test/test_curses.py
.ss......ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss Ran 71 tests in 0.121s OK (skipped=64) (When TERM is defined - a core dump still occurs - that will be a new issue and a new PR). |
backports needed for 3.8 and 3.9 |
Minor correction. update_lines_cols() is not provided by the underlying curses library, it is a helper defined in Python wrapper. But it is optional, snd skipping test is the correct solution. Thank you. As for the core dump, could you please run the test in verbose mode with redirected stdout and stderr and show the result?
What is the default value of TERM? Does the result differ if set TERM=xterm? |
my default TERM=xterm I'll also use 'ansi' The filenames will be ${TERM}.err and ${TERM}.out for TERM in xterm ansi; do After TERM=ansi - my terminal is in raw mode (i.e., needed). |
Thank you. I see that 7 tests are failed (test_background, test_color_attrs, test_color_content, test_getch, test_getstr, test_init_pair, test_insert_delete) and test_output_string perhaps crashes. Could you please run tests with test_insert_delete skipped (option -i test_insert_delete or just skip in code)? If it crashes on other tests, skip them as well. |
Please also try to comment out the following line in test_output_string. Does it help?
|
./python -m test -vuall -i test_output_string -i test_insert_delete test_curses 2>test.err 1>test.out returns four failures: see attached '-i test_output_string' stops the crash |
FYI: from a core dump - top of where is: Segmentation fault in winsnstr at 0xd3ebc050 |
Dome some 'dumb' testing - and I hope this helps understand why it is failing: With the the last two func() calls commented out, the function passes: def test_output_string(self):
stdscr = self.stdscr
encoding = stdscr.encoding
# addstr()/insstr()
for func in [stdscr.addstr, stdscr.insstr]:
with self.subTest(func.__qualname__):
stdscr.move(0, 0)
func('abcd')
func(b'abcd')
s = 'à▒^▒ç▒^▒'
try:
func(s)
except UnicodeEncodeError:
self.assertRaises(UnicodeEncodeError, s.encode, encoding)
func('abcd', curses.A_BOLD)
# func(1, 2, 'abcd')
# func(2, 3, 'abcd', curses.A_BOLD) |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: