Update inigo to reflect several code changes and make things less flaky.

- Pass RepID to reprunner
- Use rata instead of router
- Make app start spec less flaky (look for more reliable output)
- Switch from Script to Path, Args
bump deps
Allow dev-test script to pass args to ginkgo

Signed-off-by: Ted Young <tyoung@pivotallabs.com>
repID -> executorID

Signed-off-by: Ted Young <tyoung@pivotallabs.com>
bump deps
consume the inigo server output stream

previously the client would lock up sending back the process payloads, and
keep the connection open.

Signed-off-by: Alex Suraci <asuraci@pivotallabs.com>
simplify inigo server; don't need NetOut

Signed-off-by: Alex Suraci <asuraci@pivotallabs.com>
wait a bit longer for warden to shut down

this involves destroying containers; 5 seconds cuts it a bit close

Signed-off-by: Alex Suraci <asuraci@pivotallabs.com>
use $GOPATH_ROOT rather than first $GOPATH

Signed-off-by: Sheel Choksi <sheelc@pivotallabs.com>
use unix rather than tcp for warden

Signed-off-by: Sheel Choksi <sheelc@pivotallabs.com>
deps

Signed-off-by: Sheel Choksi <sheelc@pivotallabs.com>
update inigo server garden api usage

Signed-off-by: Sheel Choksi <sheelc@pivotallabs.com>
Add resource flags to stager test

Signed-off-by: Max Brunsfeld <mbrunsfeld@pivotallabs.com>
Rename stager resource limit flags

Also, pass the same flags to the other stager runner in the
test for 'two stagers running'

Signed-off-by: Max Brunsfeld <mbrunsfeld@pivotallabs.com>
make loggregator test less flaky

expand loggredile gbytes api and hide channel-based api now that no one uses
it

Signed-off-by: Sheel Choksi <sheelc@pivotallabs.com>
remove expensive assertion

this doesn't seem to be related to the example that's been set up; seems to
guard against more than one stager processing a request, which we test
elsewhere.

Signed-off-by: Abhijit Hiremagalur <abhi@pivotallabs.com>
use LONG_TIMEOUT in eventually, 10 in consistently

for consistently, the value given is time for assurance, not time after which
to give up. as we bump the 'give up' timeout (i.e. for testing on systems
under load), the consistency checks should not take any longer.

in this case, it's testing that things don't happen concurrently, and so the
next assertion should have happened around the same amount of time.

Signed-off-by: Abhijit Hiremagalur <abhi@pivotallabs.com>
clean-up timeouts, set defaults using Gomega's default timeouts
add environment variable to tweak default eventually timeout
fix loggregator package name

Signed-off-by: Alex Suraci <asuraci@pivotallabs.com>