Describe how to set up for local testing

This depends on a valid Docker base image being available as
referenced by the FROM statement in integration/rootfs/Dockerfile.

The performance measurements tests give rise to some arithmetic
overflows and seem unstable and so are omitted from these
instructions.
Install ginkgo without changing directories
Merge pull request #5 from glyn/test-setup

Describe how to set up for local testing
garden runner takes network and address as params

Signed-off-by: Dave Liebreich <dliebreich@pivotallabs.com>
fix integration test garden_runner usage

Signed-off-by: Alex Suraci <asuraci@pivotallabs.com>
start.sh: don't silence wsh output; tee instead

Signed-off-by: Alex Suraci <asuraci@pivotallabs.com>
implement timeout waiting for iomux-link
  * -t <timeout in seconds>
  * must be first thing on command line
  * default timeout is 5 seconds

Signed-off-by: Ted Young <tyoung@pivotallabs.com>
don't compile garden in garden runner

tests using it may want to tweak e.g. gopath and args
bump deps
fix integration tests
Fix compiler warnings

These showed up on RHEL 7, but may have been present previously.
Unmount mount points when cleaning up a container's filesystem

In some circumstances these mount points prevent the subsequent rm -rf
commands from working (they fail with 'device busy'). Unmounting them
explicitly avoids that. This was encountered on RHEL 7.
Test suite robustness

Ensure clean up occurs on panic.

Cleanup and terminate on interrupt.

Note: GardenRunner.Stop and .TearDown should be idempotent, even if
they aren’t yet.
GardenRunner support for premature process termination

If garden has already terminated when we attempt to interrupt it,
do not treat this as an error and proceed to check that garden
really has terminated.

The two cases referred to in the code are discussed here:

https://groups.google.com/forum/#!searchin/golang-nuts/Process.signal$20behaviour/golang-nuts/2Zmut0tcnPE/wIsFGWmWz1MJ