Switch test_bucket_list_maxkeys_unreadble to use '\n' instead of '\a'.

This avoids the SAX parser error. It also gave a different error code
from Amazon.

diff --git a/s3tests/functional/test_s3.py b/s3tests/functional/test_s3.py
index 316f8407e1de5283a5f894f23313149b7871de2d..818d28d44ca5c139cec92d7cb38955df0ba4d29e 100644 (file)
--- a/s3tests/functional/test_s3.py
+++ b/s3tests/functional/test_s3.py
@@ -387,13 +387,13 @@ def test_bucket_list_maxkeys_invalid():
 def test_bucket_list_maxkeys_unreadable():
     bucket = _create_keys(keys=['bar', 'baz', 'foo', 'quxx'])
 
-    e = assert_raises(boto.exception.S3ResponseError, bucket.get_all_keys, max_keys='\x07')
+    e = assert_raises(boto.exception.S3ResponseError, bucket.get_all_keys, max_keys='\x0a')
     eq(e.status, 400)
     eq(e.reason, 'Bad Request')
     # Weird because you can clearly see an InvalidArgument error code. What's
     # also funny is the Amazon tells us that it's not an interger or within an
     # integer range. Is 'blah' in the integer range?
-    eq(e.error_code, None)
+    eq(e.error_code, 'InvalidArgument')
 
 
 @attr('fails_on_rgw')