It turns out test_curses can fail in a 2.6 buildbot because stdout is not

a tty in certain cases.

Merged revisions 75518 via svnmerge from
svn+ssh://pythondev@svn.python.org/python/trunk

........
  r75518 | r.david.murray | 2009-10-19 12:01:28 -0400 (Mon, 19 Oct 2009) | 3 lines

  Only run test_curses when sys.__stdout__ is a tty.  This eliminates the
  last false positive when running regrtest with -j.
........
This commit is contained in:
R. David Murray 2009-11-03 14:31:53 +00:00
parent bb6c433409
commit 24b19992d2
1 changed files with 2 additions and 0 deletions

View File

@ -269,6 +269,8 @@ if __name__ == '__main__':
curses.wrapper(main) curses.wrapper(main)
unit_tests() unit_tests()
else: else:
if not sys.__stdout__.isatty():
raise unittest.SkipTest("sys.__stdout__ is not a tty")
# testing setupterm() inside initscr/endwin # testing setupterm() inside initscr/endwin
# causes terminal breakage # causes terminal breakage
curses.setupterm(fd=sys.__stdout__.fileno()) curses.setupterm(fd=sys.__stdout__.fileno())