From 61792348039db8f6d5700b3a92a5150e84a61a85 Mon Sep 17 00:00:00 2001 From: Neal Norwitz Date: Sun, 27 Jan 2008 05:02:56 +0000 Subject: [PATCH] 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. --- Lib/test/test_resource.py | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/Lib/test/test_resource.py b/Lib/test/test_resource.py index 28876e3a211..86c7cc206ab 100644 --- a/Lib/test/test_resource.py +++ b/Lib/test/test_resource.py @@ -37,8 +37,11 @@ try: f.write("Y") f.flush() # On some systems (e.g., Ubuntu on hppa) the flush() - # doesn't cause the exception, but the close() does. - f.close() + # doesn't always cause the exception, but the 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: if not limit_set: raise