1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

test: put tty in blocking mode after test

Browse Source 
Tests can leave the tty in non-blocking mode. If the test runner tries
to print to stdout/stderr after that and the tty buffer is full, it'll
die with a EAGAIN OSError. Ergo, put the tty back in blocking mode
before proceeding.
This commit is contained in:
Ben Noordhuis 2013-01-07 03:59:08 +01:00
parent 4e1a2f9a89
commit fa3bfc3a66
1 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
tools/test.py
View File

@ -400,10 +400,20 @@ class TestCase(object):
def Run(self): def Run(self):
self.BeforeRun() self.BeforeRun()
try: try:
result = self.RunCommand(self.GetCommand()) result = self.RunCommand(self.GetCommand())
finally: finally:
self.AfterRun(result) # Tests can leave the tty in non-blocking mode. If the test runner
# tries to print to stdout/stderr after that and the tty buffer is
# full, it'll die with a EAGAIN OSError. Ergo, put the tty back in
# blocking mode before proceeding.
if sys.platform != 'win32':
from fcntl import fcntl, F_GETFL, F_SETFL
from os import O_NONBLOCK
for fd in 0,1,2: fcntl(fd, F_SETFL, ~O_NONBLOCK & fcntl(fd, F_GETFL))
self.AfterRun(result)
return result return result
def Cleanup(self): def Cleanup(self):