Tightening up CI Integration

[devoxel]

I think the current test architecture needs a re-examination.

I've identified a couple of issues:

Verbose Logs

Logs are verbose.

$ curl https://s3.amazonaws.com/archive.travis-ci.org/jobs/85403103/log.txt | wc -l
15385

Ouch. Take a step back: that's literally unreadable.

Tests are slow

Take a look at the travis-ci build history

Every build runs for about 5hrs and runs in a single command. Compare that to the ruby on rails setup. Builds are separated based on what's being tested and things are allowed to fail (namely some tests with new versions of ruby)

---

I suggest fixing these by making these changes:

• Separating tests into canonical pieces
• Allowing some tests to fail, be it because of network errors, 404s or just non-core functionality

I'm going to start on this stuff on a fork, but I'd like community input too so do shout at me.