Running the live tests

[David Cheney]

Do you have the output from your test run ?

Why are the live tests unreliable -- IMHO, because we don't run them 
constantly, because they are very slow, and unreliable.

If you can bootstrap --upload-tools from this environment, then that is 
similar enough to the live tests to be sufficient to commit.

On 18/03/13 14:11, Tim Penhey wrote:
> Hi All,
>
> Today I had my first go at running the live tests.
>
> It isn't documented anywhere (at least not where I looked) on how to run
> the live tests.  I'm considering adding this to the tree somewhere,
> perhaps docs/testing.txt.
>
> What I ended up doing was:
>    $ cd $GOPATH/src/launchpad.net/juju-core/environs/ec2
>    $ time go test -test.timeout=1200s -amazon
>
> I run the suite three times.  The time taken ranged between 15 and 20
> minutes, and I got no clean runs.
>
> Over the three different runs I did however get successful runs of all
> the tests, but not all at the same time.
>
> What is the expected behaviour here?
>
> Do we know why the tests are not consistently passing?  Is it due to how
> the tests are written, or is it generally EC2 stuff?  If it is EC2
> issues, how could we change the tests to pass more consistently?
>
> Cheers,
> Tim
>