https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.40.0 2019-09-16T18:43:23+00:00 2019-09-16T18:43:23+00:00 Alex Crichton alex@alexcrichton.com 2019-09-16T18:43:23+00:00 urn:sha1:821d293283f939272efecf8dd8c401c818c4428d This commit disables LLVM/debug assertions in our 5 slowest builders: * i686-gnu * i686-gnu-nopt * i686-msvc-1 * i686-msvc-2 * x86_64-msvc-cargo This is reducing the amount of test coverage for LLVM/debug assertions, but we're just unfortunately running out of time on CI too many times. Some test builds have shown that i686-gnu drops nearly an hour of CI time by disabling these two assertions. Perhaps when we eventually get 4-core machines we can reenable these, but for now turn them off and hook them up to the tracking issue at #59637 which will ideally be repurposes to tracking all of these. 2019-05-30T14:28:56+00:00 Alex Crichton alex@alexcrichton.com 2019-05-30T14:22:53+00:00 urn:sha1:ebdf42e9650a969bef553a0886d3754a670bd335 Since #61212 we've been timing out on OSX, and this looks to be because we're building tools like Cargo and the RLS twice instead of once. This turns out to be a slight bug in our configuration. CI builders using the `RUST_CHECK_TARGET` directive actually execute `make all` just before their acual target. In `make all` we're building a stage2 cargo, and then in `make dist` we're building a stage1 cargo. Other builders use `SCRIPT` which provides explicit control over what `x.py` script, for example, is used to execute the build. This moves almost all targets to using `SCRIPT` to ensure that we're explicitly specifying what's being built where. Additionally this updates the logic of `RUST_CHECK_TARGET` to remove the pre-flight tidy as well as the pre-flight `make all`. The system LLVM builder (run on PRs) now explicitly runs tidy first and then runs the rest of the test suite. 2017-08-27T01:34:13+00:00 Alex Crichton alex@alexcrichton.com 2017-08-27T01:34:13+00:00 urn:sha1:ffe64a26abb194a7ddcc5f410512043a65b3eb91 Newer versions of Docker have a `--init` argument which spawns an init process in the container, which we should be able to use everywhere now. 2017-07-13T01:25:36+00:00 Ty Coghlan Coghlan.Ty@gmail.com 2017-07-09T15:01:27+00:00 urn:sha1:250346128b0083c8137171af503bda194c6124dd 2017-05-12T16:07:10+00:00 Alex Crichton alex@alexcrichton.com 2017-05-12T16:07:10+00:00 urn:sha1:c30e007b86aa7aedd15e590d7ad41914ff823d23 This commit updates the sccache binaries to fix a cache load failure seen on #41926, fixed by mozilla/sccache#119 2017-04-29T07:29:54+00:00 Alex Crichton alex@alexcrichton.com 2017-04-29T07:29:54+00:00 urn:sha1:aa891a57a11da2845352e9ed093a1cd85f377289 Pulls in mozilla/sccache@ef0d77543 to fix #40240 again after the builds included in #41447 forgot to include the mio fixed included in #41076. Closes #40240 2017-04-27T14:19:34+00:00 Alex Crichton alex@alexcrichton.com 2017-02-25T17:53:46+00:00 urn:sha1:2e72bcb9347aa1bafe63c4a64a824ac091babfd8 Now that the final bug fixes have been merged into sccache we can start leveraging sccache on the MSVC builders on AppVeyor instead of relying on the ad-hoc caching strategy of trigger files and whatnot. 2017-04-27T14:18:01+00:00 Alex Crichton alex@alexcrichton.com 2017-04-19T15:58:27+00:00 urn:sha1:499b84aca8b9e501d7def82a1f483e77ac4199ff This build is no longer a forked version with temporary bugfixes, everything should be upstreamed! 2017-04-04T22:55:23+00:00 Alex Crichton alex@alexcrichton.com 2017-04-04T22:55:23+00:00 urn:sha1:e60ea55f660bfd0d34fc18efa60b2d9764840601 I've tracked down what I believe is the last spurious sccache failure on #40240 to behavior in mio (carllerche/mio#583), and this commit updates the binaries to a version which has that fix incorporated. 2017-03-25T02:00:35+00:00 Alex Crichton alex@alexcrichton.com 2017-03-25T02:00:35+00:00 urn:sha1:bff332e0a22ce71f329202fc635693079e791bb5 Looks like the last version was built with mio 0.6.5 which now has known bugs against it. This build includes mio 0.6.6