6 ms·
> Today the longest-running configuration takes over 2 hours. I'm curious which configuration that is, and how it could be accelerated.
by JoshTriplett 9y ago
> Today the longest-running configuration takes over 2 hours.
I'm curious which configuration that is, and how it could be accelerated.
- sanxiyn 9y agoFYI, it's i686-apple-darwin at the moment.
- steveklabnik 9y agoLooking at the build that's building right now, all of them have passed but one, which has been going on for 2 hours and 23 minutes: https://travis-ci.org/rust-lang/rust/builds/252052639 https://travis-ci.org/rust-lang/rust/builds/252052639 > "env": "RUST_CHECK_TARGET=dist RUST_CONFIGURE_ARGS=\"--target=aarch64-apple-ios,armv7-apple-ios,armv7s-apple-ios,i386-apple-ios,x86_64-apple-ios --enable-extended --enable-sanitizers --enable-profiler\" SRC=. DEPLOY=1 RUSTC_RETRY_LINKER_ON_SEGFAULT=1 SCCACHE_ERROR_LOG=/tmp/sccache.log MACOSX_DEPLOYMENT_TARGET=10.7\n", iOS, it seems. Looking at the other builds, * s390x Linux * i686-apple-darwin * x86_64-apple-darwin Seems apple is an overall slowpoke.
- sanxiyn 9y agoIt seems to vary from build to build... Compare https://travis-ci.org/rust-lang/rust/builds/251809226 https://travis-ci.org/rust-lang/rust/builds/251809226 where everything is under 2 hours except i686-apple-darwin.
- ihsw2 9y agoThis has more to do with Travis-CI than Darwin et al. https://www.traviscistatus.com/ https://www.traviscistatus.com/ Notice how the active OS X builds reaches the limit of 216 jobs and the backlog of OS X jobs increases without decreasing. This is a capacity issue that is likely related to high OS X build costs. Another thing to notice is that the backlog correlates strongly with time of day in the EST timezone, where the backlog starts to take off after 9am EST.
- ihsw2 9y agoAs mentioned elsewhere in this thread, it stands to reason that Travis-CI is the culprit here. https://www.traviscistatus.com/ https://www.traviscistatus.com/ Their slowest build jobs are all on Darwin/OSX-based systems and (notably) this is a problem numerous other projects have -- slow jobs on OSX build systems. There is a large backlog of OSX build jobs that starts around 9am EST.
- JoshTriplett 9y agoIs that true for the paid version of Travis as well? If not, might be worth paying for it, to support a community as large as Rust's. (If the paid version is that backlogged as well, I'm surprised they don't put more resources into accelerating it; perhaps not enough of their customers care about macOS?) Alternatively, given that Mozilla has their own extensive CI infrastructure (for Firefox), perhaps it'd make sense to migrate to that instead of Travis?
- steveklabnik 9y agoWe are already paying Travis. > Given that Mozilla has their own extensive CI infrastructure While Mozilla does sponsor a lot of Rust stuff, it's fundamentally a community project, and so many of us (including myself) would prefer to not to move closer to something that's Mozilla-specific.
- JoshTriplett 9y agoThanks for the explanations. > We are already paying Travis. Have you heard anything from them about improving the issues with macOS? You've certainly got a case study in it being a problem. > While Mozilla does sponsor a lot of Rust stuff, it's fundamentally a community project, and so many of us (including myself) would prefer to not to move closer to something that's Mozilla-specific. Fair enough; I only suggested it because I had the impression that Mozilla's bits were all based on Open Source systems, and it would just be a matter of sharing hosting infrastructure rather than duplicating it.
- 9y ago