Join GitHub today
only cargo-check integration tests on travis and appveyor #911
We've started to regularly run into the Travis time-outs again.
Since the integration tests are not being run, but only compiled (and then the compilation results discarded as the build exits), this PR changes the Travis and Appveyor tests to only
I would advocate that for running integration tests in CI at a later point we use a separate pipeline (maybe use CircleCI or a custom Jenkins setup rather than chucking it on top of the existing ones), so we have a clean separation of concerns and keep the build times in check.