When running ./test --functional (the errors also occur if you run ./test without options, but --functional makes it fail quicker), I see a whole mess of errors. This looks to be because my AWS credentials aren't in the global environment. For example:
Traceback (most recent call last):
File "/home/graham/launchpad/workspace/juju/trunk/juju/ftests/test_ec2_provider.py", line 218, in setUp
super(EC2StorageTest, self).setUp()
File "/home/graham/launchpad/workspace/juju/trunk/juju/ftests/test_ec2_provider.py", line 114, in setUp "juju-branch": juju_branch})
File "/home/graham/launchpad/workspace/juju/trunk/juju/providers/ec2/__init__.py", line 37, in __init__
s3_uri=config.get("s3-uri", ""))
File "/usr/lib/python2.7/dist-packages/txaws/service.py", line 102, in __init__
creds = AWSCredentials(access_key, secret_key)
File "/usr/lib/python2.7/dist-packages/txaws/credentials.py", line 34, in __init__
raise ValueError("Could not find %s" % ENV_ACCESS_KEY)
exceptions.ValueError: Could not find AWS_ACCESS_KEY_ID
I've attached the full output from ./test --functional for reference.
I believe that the functional tests actually do require the use of EC2, so it doesn't look like this is an actual issue.
As Clint points out, the message could be improved, though, and the traceback avoided.