Shippable fails to run unit tests

[tgross]

https://app.shippable.com/runs/57ebded26fb4bc0e008f22d3/1/console

docker run --rm -w /usr/local/bin \
        -e LOG_LEVEL=DEBUG \
        -v /root/src/github.com/autopilotpattern/mysql/bin/manager:/usr/local/bin/manager \
        -v /root/src/github.com/autopilotpattern/mysql/bin/manage.py:/usr/local/bin/manage.py \
        -v /root/src/github.com/autopilotpattern/mysql/bin/test.py:/usr/local/bin/test.py \
        autopilotpattern/mysql:master-fdd92a1c2096ffbaf746e102c026cd42c64b8aa2 \
        python test.py
Timestamp: 2016-09-28 15:25:09.780142711 +0000 UTC
Code: System error

Message: not a directory

Frames:

---
0: setupRootfs
Package: github.com/opencontainers/runc/libcontainer
File: rootfs_linux.go@40

---
1: Init
Package: github.com/opencontainers/runc/libcontainer.(*linuxStandardInit)
File: standard_init_linux.go@57

---
2: StartInitialization
Package: github.com/opencontainers/runc/libcontainer.(*LinuxFactory)
File: factory_linux.go@242

---
3: initializer
Package: github.com/docker/docker/daemon/execdriver/native
File: init.go@35

---
4: Init
Package: github.com/docker/docker/pkg/reexec
File: reexec.go@26

---
5: main
Package: main
File: docker.go@18

---
6: main
Package: runtime
File: proc.go@63

---
7: goexit
Package: runtime
File: asm_amd64.s@2232
Error response from daemon: Cannot start container 68f0db235ad6fe4bd6215971a36e7701bf9e9be675dcdd2f9085e7a2896c0d54: [8] System error: not a directory
make: *** [unit-test] Error 1

This error message usually means there's something wrong in the -v arguments. This runs locally just fine so I'll have to investigate what's up with that. Relevant section of the makefile is:

    docker run --rm -w /usr/local/bin \
        -e LOG_LEVEL=DEBUG \
        -v $(shell pwd)/bin/manager:/usr/local/bin/manager \
        -v $(shell pwd)/bin/manage.py:/usr/local/bin/manage.py \
        -v $(shell pwd)/bin/test.py:/usr/local/bin/test.py \
        autopilotpattern/mysql:$(TAG) \
        python test.py

[tgross]

I've got unit tests running now via 42333badba31e9e3c26a89fe6ff3196b28e286d0. But now the integration tests appear to be passing but then Shippable is halting the test run after what might be a hang? (ref https://app.shippable.com/runs/57ed794550f20d10005dc84d/1/console) I'm looking into this next.

[tgross]

Running these via our Jenkins CI runner now.