Merge lp://staging/~vila/uci-engine/integration-speed-up into lp://staging/uci-engine

Teach AmuletDeployment() to skip the deployment when one is already available.

This changes lp:~doanac/uci-engine/integration-speed-up to minimize the scope of the workaround.

Andy, we've been talking past each other I think, let me restart the discussion:

1) We are bitten hard by https://bugs.launchpad.net/juju-core/+bug/1200267

IMO, It's the most important issue we face for the current "integration" tests: I thought you had some insight about what was going on hence my question. You don't. Damn. Me neither. Damn damn.

I don't want this issue to get out of our radar hence the comment in setUp() in this proposal. If we kick the can, let's make sure it's still in front of us.

2) We need a workaround in the mean time.

I'm fine with that but I want that workaround to be expressed in the right place: at the test level.

I want (like you), as a dev, to be in charge of the environment where my test run.

I *don't* want to have to tell the test runner about that.

You proposed to use an env var for that, there is no need for a class
attribute to duplicate that information.

bzr diffstat for this proposal is:

  1 file changed, 14 insertions(+), 10 deletions(-)

yours was:

    8 files changed, 26 insertions(+), 31 deletions(-)

I don't want to carry those additional changes.