Get PR builds to finish in under 5 minutes about angle-grinder HOT 6 CLOSED

It looks like most of that time is spent in Docker containers. Cargo's cache doesn't get copied into them AFAIK, so it will spend the time downloading and compiling every dependency for every arch for every build. Is it enough to cargo build --target <target arch>, or should/must the tests be run against that arch? If you just wanted a successful build, you could let Travis keep the build cache for a target.

A bandaid I can think of right now is defining a build matrix in the Travis config so each arch is at least built and tested in parallel. I haven't had good luck exposing Cargo caches to Docker containers, but it might worth a shot with a volume mapping.

from angle-grinder.

For pull requests, I'm fine only running the tests directly on linux without using docker.

When travis has containers available, we each arch does get built and tested in parallel, so the wall-clock time to results is "only" 30 minutes

from angle-grinder.

I am a bit confused over what cross is doing in there tbh. Unless I am really misunderstanding how Travis is configured, it looks like each platform is built on its native OS type, so cross isn't really achieving anything at present. (So on linux, host os is linux and cross targets x86_64-unknown-linux-musl; on OS X, host OS is OS X and cross targets x86_64-darwin-whatever-the-rest-of-the-tuple-is.)

I'm not sure if this impacts build time however. Happy to look though, it would be basically applying the flow I've put in the Windows Build PR to the other platforms as well.

Generally when I need quick CI my first response is "set up CircleCI", not sure if you are up for such a change though. :) You'd need to stick with cross then though, afaik it only supports Linux host OSes. There may also be issues because CircleCI itself uses Docker heavily in order to get its startup times so quick.

Additionally, when I was testing, I think the cache is acting per-branch. So updates to a PR would be down to normal times, but each new PR is currently quite a slow build. I'm not sure if this is by design in Travis or if it's configurable (or if it's a bug...)

from angle-grinder.

Additionally, when I was testing, I think the cache is acting per-branch. So updates to a PR would be down to normal times, but each new PR is currently quite a slow build. I'm not sure if this is by design in Travis or if it's configurable (or if it's a bug...)

From the travis docs,

If a branch does not have its own cache, Travis CI fetches the default branch cache.

I'm not sure if that's something I have to setup manually, but it seems like branches should get a cache on first-built

from angle-grinder.

I made some tweaks in #54 that get PR builds down to 10 minutes, a decent improvement

from angle-grinder.

I have no idea what happened, maybe something on Travis? Anyway, builds now finish in 3 minutes!

from angle-grinder.