#1291: copy test_resource.py from the 2.6 trunk, to fix a test failure.

The 2.6 version also converts to unittest, but it seems to work fine under 2.5.
This commit is contained in:
Andrew M. Kuchling 2008-02-23 21:32:06 +00:00
parent 664553a778
commit 310bad077b
1 changed files with 102 additions and 63 deletions

View File

@ -1,71 +1,110 @@
import os import unittest
from test import test_support
import resource import resource
import time
from test.test_support import TESTFN, unlink # This test is checking a few specific problem spots with the resource module.
# This test is checking a few specific problem spots. RLIMIT_FSIZE class ResourceTest(unittest.TestCase):
# should be RLIM_INFINITY, which will be a really big number on a
# platform with large file support. On these platforms, we need to
# test that the get/setrlimit functions properly convert the number to
# a C long long and that the conversion doesn't raise an error.
try: def test_args(self):
cur, max = resource.getrlimit(resource.RLIMIT_FSIZE) self.assertRaises(TypeError, resource.getrlimit)
except AttributeError: self.assertRaises(TypeError, resource.getrlimit, 42, 42)
pass self.assertRaises(TypeError, resource.setrlimit)
else: self.assertRaises(TypeError, resource.setrlimit, 42, 42, 42)
print resource.RLIM_INFINITY == max
resource.setrlimit(resource.RLIMIT_FSIZE, (cur, max))
# Now check to see what happens when the RLIMIT_FSIZE is small. Some def test_fsize_ismax(self):
# versions of Python were terminated by an uncaught SIGXFSZ, but
# pythonrun.c has been fixed to ignore that exception. If so, the
# write() should return EFBIG when the limit is exceeded.
# At least one platform has an unlimited RLIMIT_FSIZE and attempts to
# change it raise ValueError instead.
try:
try:
resource.setrlimit(resource.RLIMIT_FSIZE, (1024, max))
limit_set = 1
except ValueError:
limit_set = 0
f = open(TESTFN, "wb")
try:
f.write("X" * 1024)
try: try:
f.write("Y") (cur, max) = resource.getrlimit(resource.RLIMIT_FSIZE)
f.flush() except AttributeError:
# On some systems (e.g., Ubuntu on hppa) the flush() pass
# doesn't always cause the exception, but the close() else:
# does eventually. Try flushing several times in # RLIMIT_FSIZE should be RLIM_INFINITY, which will be a really big
# an attempt to ensure the file is really synced and # number on a platform with large file support. On these platforms,
# the exception raised. # we need to test that the get/setrlimit functions properly convert
for i in range(5): # the number to a C long long and that the conversion doesn't raise
time.sleep(.1) # an error.
f.flush() self.assertEqual(resource.RLIM_INFINITY, max)
except IOError:
if not limit_set:
raise
if limit_set:
# Close will attempt to flush the byte we wrote
# Restore limit first to avoid getting a spurious error
resource.setrlimit(resource.RLIMIT_FSIZE, (cur, max)) resource.setrlimit(resource.RLIMIT_FSIZE, (cur, max))
finally:
f.close()
finally:
if limit_set:
resource.setrlimit(resource.RLIMIT_FSIZE, (cur, max))
unlink(TESTFN)
# And be sure that setrlimit is checking for really large values def test_fsize_enforced(self):
too_big = 10L**50 try:
try: (cur, max) = resource.getrlimit(resource.RLIMIT_FSIZE)
resource.setrlimit(resource.RLIMIT_FSIZE, (too_big, max)) except AttributeError:
except (OverflowError, ValueError): pass
pass else:
try: # Check to see what happens when the RLIMIT_FSIZE is small. Some
resource.setrlimit(resource.RLIMIT_FSIZE, (max, too_big)) # versions of Python were terminated by an uncaught SIGXFSZ, but
except (OverflowError, ValueError): # pythonrun.c has been fixed to ignore that exception. If so, the
pass # write() should return EFBIG when the limit is exceeded.
# At least one platform has an unlimited RLIMIT_FSIZE and attempts
# to change it raise ValueError instead.
try:
try:
resource.setrlimit(resource.RLIMIT_FSIZE, (1024, max))
limit_set = True
except ValueError:
limit_set = False
f = open(test_support.TESTFN, "wb")
try:
f.write("X" * 1024)
try:
f.write("Y")
f.flush()
# On some systems (e.g., Ubuntu on hppa) the flush()
# doesn't always cause the exception, but the close()
# does eventually. Try flushing several times in
# an attempt to ensure the file is really synced and
# the exception raised.
for i in range(5):
time.sleep(.1)
f.flush()
except IOError:
if not limit_set:
raise
if limit_set:
# Close will attempt to flush the byte we wrote
# Restore limit first to avoid getting a spurious error
resource.setrlimit(resource.RLIMIT_FSIZE, (cur, max))
finally:
f.close()
finally:
if limit_set:
resource.setrlimit(resource.RLIMIT_FSIZE, (cur, max))
test_support.unlink(test_support.TESTFN)
def test_fsize_toobig(self):
# Be sure that setrlimit is checking for really large values
too_big = 10L**50
try:
(cur, max) = resource.getrlimit(resource.RLIMIT_FSIZE)
except AttributeError:
pass
else:
try:
resource.setrlimit(resource.RLIMIT_FSIZE, (too_big, max))
except (OverflowError, ValueError):
pass
try:
resource.setrlimit(resource.RLIMIT_FSIZE, (max, too_big))
except (OverflowError, ValueError):
pass
def test_getrusage(self):
self.assertRaises(TypeError, resource.getrusage)
self.assertRaises(TypeError, resource.getrusage, 42, 42)
usageself = resource.getrusage(resource.RUSAGE_SELF)
usagechildren = resource.getrusage(resource.RUSAGE_CHILDREN)
# May not be available on all systems.
try:
usageboth = resource.getrusage(resource.RUSAGE_BOTH)
except (ValueError, AttributeError):
pass
def test_main(verbose=None):
test_support.run_unittest(ResourceTest)
if __name__ == "__main__":
test_main()