Backport 60342:

Try to prevent this test from being flaky.  We might need a sleep in here
which isn't as bad as it sounds.  The close() *should* raise an exception,
so if it didn't we should give more time to sync and really raise it.
This commit is contained in:
Neal Norwitz 2008-01-27 05:02:56 +00:00
parent ab577c1b32
commit 6179234803
1 changed files with 5 additions and 2 deletions

View File

@ -37,8 +37,11 @@ try:
f.write("Y") f.write("Y")
f.flush() f.flush()
# On some systems (e.g., Ubuntu on hppa) the flush() # On some systems (e.g., Ubuntu on hppa) the flush()
# doesn't cause the exception, but the close() does. # doesn't always cause the exception, but the close()
f.close() # does eventually. Try closing several times in an attempt
# to ensure the file is really synced and the exception raised.
for i in range(5):
f.close()
except IOError: except IOError:
if not limit_set: if not limit_set:
raise raise