[issue15664] test_curses not run with 'make test'

2012-08-15 Thread Nadeem Vawda
Changes by Nadeem Vawda : -- superseder: -> test_curses skipped on buildbots ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue15664] test_curses not run with 'make test'

2012-08-15 Thread Ronald Oussoren
Ronald Oussoren added the comment: Yes. I'll add a message to that issue to note that is also affects 'make test' -- resolution: -> duplicate stage: -> committed/rejected status: open -> closed type: -> behavior ___ Python tracker

[issue15664] test_curses not run with 'make test'

2012-08-15 Thread R. David Murray
R. David Murray added the comment: So this should be closed as a duplicate of issue 12669? -- nosy: +r.david.murray ___ Python tracker ___ ___

[issue15664] test_curses not run with 'make test'

2012-08-15 Thread Ronald Oussoren
Ronald Oussoren added the comment: I knew the test failure looked familiar, but couldn't find the issue in the tracker. This issue (test_curses not running with make test) is due to '-j0' in the arguments to the test runner: with -j0 the runner uses multiprocessing and the stdout and stderr

[issue15664] test_curses not run with 'make test'

2012-08-15 Thread Ned Deily
Ned Deily added the comment: The "chr() arg not in range(0x11)" from test_unget_wch is due to a bug in ncurses < 5.8; see Issue15037. -- ___ Python tracker ___ _

[issue15664] test_curses not run with 'make test'

2012-08-15 Thread Ronald Oussoren
Ronald Oussoren added the comment: the test does get run with 'make buildbottest', and then fails with a ValueError exception: $ /Users/ronald/Projects/python/rw/default/tbuild/python.exe -W default -bb -E -R -m test -r -w -j 1 -u all -W --timeout=3600 test_curses Using random seed 2242495 [1

[issue15664] test_curses not run with 'make test'

2012-08-15 Thread Ned Deily
Ned Deily added the comment: This appears to be the same issue as raised in Issue12669. Apparently it is not fixed. -- nosy: +ned.deily ___ Python tracker ___ _

[issue15664] test_curses not run with 'make test'

2012-08-15 Thread Ronald Oussoren
New submission from Ronald Oussoren: I noticed that 'test_curses' is not started when performing "make test" on an OSX box: ... [ 42/369] test_curses test_curses skipped -- sys.__stdout__ is not a tty ... The host is a machine running OSX 10.8, fully up-to-date with patches and the current ve