Add tox startup (run.sh) test and test on OS X and linux

[mvdbeek]

This fetches @jmchilton's sqlite template, runs common_startup.sh and run.sh, and checks that curl can contact galaxy. On the .travis.yml side, this test is run on linux and os x.

[martenson]

very nice @mvdbeek !

[jmchilton]

What a wonderful idea, this is awesome.

It is unrelated to this PR so feel free to ignore the request, but I will grant bonus points if you update the travis matrix to run the py27 unit tests under Mac OS X also.

[mvdbeek]

Yay! Bonus Points !! 💰
The startup test on osx is supposed to fail ( Issues #1633 / #1640).

[mvdbeek]

@natefoo is it to be expected that common_start.sh / run_tests.sh are still fetching pip-8.0.2+gx1 ?
https://travis-ci.org/mvdbeek/galaxy/jobs/106509804#L2522

[natefoo]

Yes, until #1652 is merged and release_16.01 is merged back to dev. After that, if you rebase this PR it should fetch 8.0.2+gx2 and the startup test on OS X should pass.

[mvdbeek]

Alright, thanks!

[mvdbeek]

Seems to work now. Should I rebase anything?
Also, I'm not sure anymore that testing run.sh is really necessary, given that #1640 would have been caught by py27-unit testing on os x.

[jmchilton]

@mvdbeek I still think exercising the recent migrations and a full start of the server is a good exercise. I like this the way it is.

[mvdbeek]

@jmchilton
Seeing issue #1563 made me think that perhaps testing run.sh on a bunch of docker images for common distributions wouldn't be the worst idea either ... but it will slow down testing.
Perhaps doing docker-based testing on wercker would be an option?

[mvdbeek]

@jmchilton
From my side this would be ready for merging.
More testing is probably worthwile (I saw at least one OS X related failure with run_tests.sh -framework (awk having slightly different options ...), but that would be a new PR.