Update travis CI for new testing schema

[jGaboardi]

Attempting to address #299

[jGaboardi]

Travis CI not kicking in, so may have bad syntax in .travis.yml

[coveralls]

Pull Request Test Coverage Report for Build 1734

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 97.854%

---

Totals
Change from base Build 1733:	0.0%
Covered Lines:	1354
Relevant Lines:	1368

---

💛 - Coveralls

[jGaboardi]

In this PR I have attempted to implement both the alternative testing structure advised by @ocefpaf while maintaining the legacy allow_failures options used when testing against the bleeding edge libpysal (PYSAL_PYPI=false) and when testing with the requirements_plus.txt soft dependencies (PYSAL_PLUS=true). Due to not being able to have named jobs through matrix expansion, it appears that all combinations must be enumerated with the include function. With this new matrix of tests (12 in total), the tarball type is tested four times. If I understand correctly, the tarball tests are simply checking the distribution (not running any other actual tests) so limiting these to one check would be acceptable. Am I correct in this?

I would appreciate any/all reviews & suggestions.

[jGaboardi]

@sjsrey Do you have any thoughts on this before merging?

@ocefpaf If you have a moment, would you be able to review this PR?

[ocefpaf]

@ocefpaf If you have a moment, would you be able to review this PR?

Sorry, I was away the past two weeks. LGMT!

PS: we should probably abstract most of that into a ci-helper so people can easily copy-n-paste it into new projects.

[jGaboardi]

@ocefpaf Thanks!

PS: we should probably abstract most of that into a ci-helper so people can easily copy-n-paste it into new projects.

For example?

[ocefpaf]

For example?

Something like https://github.com/astropy/ci-helpers. I'll try to put something together.