Test times: EC2 provider

[John Meinel]

goamz has specific retry logic to handle ec2's eventual consistency. There
isnt a flag to tweak or disable the behavior. When I brought it up in the
past, I believe Gustavo's response was that he didnt like adding a
parameter to the constructor because he didn't want people to have to think
to make things work, and he felt retrying should be done inside the library.
The test suite triggers a lot of these cases because bootstrap, etc,ook for
tools and files that don't exist (yet).

I think Gustavo was willing to take a patch that added only a boolean
"don't retry" flag.

I would be very hesitant at replacing the storage implementation inside
environs/ec2 since that is explicitly the point where we are testing the
ec2 implementation. (Arguably some tests should be about ec2 details and
not s3, but I don't feel the tests are clearly focused.)

John
=:->
On Jul 13, 2013 11:25 PM, "Jeroen Vermeulen" <jeroen.vermeulen at canonical.com>
wrote:

> It takes more than 10 minutes to run the test suite on a small cloud
> machine.  The single biggest culprit is the ec2 provider at 3 minutes,
> and I find that over 80% of that is Storage making calls to goamz.
>
> Does anyone know if perhaps there's some delay in goamz that we could
> shortcut for testing?
>
> Or alternatively, we can substitute test doubles for the Storage
> implementation now — such as a localstorage, or a simple, ultra-fast
> in-process implementation.  Might buy us a few minutes cheaply.
>
>
> Jeroen
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20130714/adbb5233/attachment.html>