Travis is failing

[bootstraponline]

I updated the docs and was surprised to see all the Travis failures.

The job exceeded the maxmimum time limit for jobs, and has been terminated.

https://travis-ci.org/google/EarlGrey/jobs/116943768

Executed 208 tests, with 2 failures (2 unexpected) in 2361.286 (2361.643) seconds

https://travis-ci.org/google/EarlGrey/jobs/116943769

[tirodkar]

Thanks for bringing this to our attention @bootstraponline, we're currently working on fixing these issues.

[bootstraponline]

Travis has a hard limit of 50 minutes for Mac builds. If there was some way to cache the app build instead of recompiling every time, that might help.

For appium, we've had to use an open source cloudbees account with on premise executors because Travis doesn't play nice with lots of UI tests.

[khandpur]

Yeah it's been pretty annoying trying to work around that. Also, Travis has a log size limit of 2 (or 3) mb I don't quite recall exactly. I switched to using xcpretty for that reason however I think xcpretty sometimes hangs or at least doesn't output stuff which makes travis believe xcodebuild is stuck for more than 10 mins and it terminates our test run.

[bootstraponline]

Yeah, another awesome feature of Travis:

If no output is received from a build for 10 minutes, it’s assumed to have stalled for unknown reasons and is subsequently killed.
https://docs.travis-ci.com/user/common-build-problems/

Probably why Swift provides their own hardware for CI. Hopefully Google has some way of provisioning Macs for builds. I wish there was an AWS like service for Mac builds (without silly timeouts).

[bootstraponline]

Travis uses MacStadium. Using them directly would mean no limits on the builds. For CI, it'd be easy to plug into a free cloudbees jenkins account.

[tirodkar]

Does this still need to be open?

[bootstraponline]

Yes, Travis is still failing.

https://travis-ci.org/google/EarlGrey

[khandpur]

Duplicate of #181