Travis build times increased 3x on macOS. Why?

travis

#1

Build times on Travis macOS increased markedly sometimes ~ 2 month ago. Example:

The Linux times stayed at ~2.5min. Any idea why? What I just saw on this run was that it hung on INFO: Computing changes... a long time (although maybe I miss-remember this up as the log suggest differently).

It might be related to recent travis macOS problems, but then I would have thought it would affect wait time but not run time.


#2

Yes, the Mac servers essentially are getting to many concurrent jobs and that’s ruining server times so they have deceased the amount of jobs any use it org can simultaneously run on Mac


#3

In my opinion, macOS CI on Travis is starting to become useless.

The inital cloning and dependency installation step (especially if there is compilation of binaries involved) alone takes longer than 15 minutes for some of my packages.

But what is the alternative? Dropping macOS CI?


#4

I advocate treating Travis for OS X as a scarce resource: if you have a good reason to use it (eg a package which is not pure Julia, has some tricky cross-platform stuff, etc) then do, otherwise disable testing for OS X until the situation is resolved.

This would result in faster test times for those who really need it, and obviously faster test times who skip these tests. The downside is not catching some subtle bugs which could crop up nevertheless. I recognize that more testing is always good, and suggest this as a practical compromise given the constraints.

I opened a related issue for PkgDev: