https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.34.0 2019-04-08T05:54:58+00:00 2019-04-08T05:54:58+00:00 Pietro Albini pietro@pietroalbini.org 2019-03-28T18:51:05+00:00 urn:sha1:d9ddef3e6df21ab70589500419a114fbf28742e3 2019-04-07T21:30:25+00:00 kennytm kennytm@gmail.com 2019-04-03T14:46:42+00:00 urn:sha1:8aa5034fb6b8f6df60fe41b9ad73c64c604ad31b 2019-04-07T20:34:21+00:00 Jeremy Soller jeremy@system76.com 2019-03-17T14:04:57+00:00 urn:sha1:16e2c163b9be2d15f48f616cd128b6f8cdf29839 2019-04-07T20:34:14+00:00 Alex Crichton alex@alexcrichton.com 2019-04-04T18:40:21+00:00 urn:sha1:54563552025958569c9aa0cb514a584ec798247f These appear to have disappeared from the original server, so I acquired the contents from a different mirror and uploaded them to our S3 bucket 2019-04-07T20:34:07+00:00 Pietro Albini pietro@pietroalbini.org 2019-04-07T11:52:33+00:00 urn:sha1:edf0ecfc0c6fc586f7456e986549cb6fefaec474 2019-02-22T19:25:14+00:00 kennytm kennytm@gmail.com 2019-02-22T18:21:41+00:00 urn:sha1:ee07b15a3c6076f31cc8085ec9274663b20b5af3 2019-02-18T17:34:14+00:00 bors bors@rust-lang.org 2019-02-18T17:34:14+00:00 urn:sha1:146aa60f3484d8267e085e80611969f387eca068 ci: fix docker cache hash collision #58416 uncovered a bug in our caching for docker images: if the image `foo` pulls files from the image `bar` and a file in `bar` changed, the hash of `foo` will be the same even though it should be different. In that PR's case, `dist-i686-linux` pulls scripts from `dist-x86_64-linux`, and the PR only changed those scripts, causing an hash collision for `dist-i686-linux`. We have to fix this, since the image will be rebuilt every time bors switches from testing master to testing beta/stable (and when it switches back), making CI way more painful than it currently is. The approach used by this PR is to just include all the files in `src/ci/docker` in the hash. It's a bit heavy-handed and it will cause a rebuild of all the images every time a single image changes, but it's the best I can think of. r? @Mark-Simulacrum cc @alexcrichton @kennytm 2019-02-18T14:28:10+00:00 Pietro Albini pietro@pietroalbini.org 2019-02-17T21:24:13+00:00 urn:sha1:2b2045d16173b3db25c74680b25cae67d41248df Before this commit the hash used to cache docker images was calculated from the image's files and the files in the scripts/ directory. This worked fine when all the files used by an image were in those directories, but some images pull files from other images, causing hash collisions in some cases. This commit changes the hash to include the files of all the docker images, causing a rebuild of all the images when a single one changes. That's a bit heavy-handed, but we have no way to track which files an image pulls in and hash collisions are really painful to deal with. 2019-02-17T14:29:33+00:00 bors bors@rust-lang.org 2019-02-17T14:29:33+00:00 urn:sha1:9a3392e174a432a5f06c1157befc1ce0fae74bec [CI] Update GCC in the dist-linux builders Upstream LLVM is planning to raise their minimum toolchain requirements, so they may start using C++14 features. This new policy has already landed in the form of a "soft" error. http://lists.llvm.org/pipermail/llvm-dev/2019-February/130117.html For GCC, they will require at least version 5.1. This PR moves our crosstool-ng builders to their max GCC 5.2, with a few small patches to fix compatibility. The dist-x86_64-linux builder is updated to GCC 5.5 and LLVM/Clang 8.0.0-rc2, which also affects dist-i686-linux sharing the same scripts. r? @alexcrichton 2019-02-15T16:20:12+00:00 bors bors@rust-lang.org 2019-02-15T16:20:12+00:00 urn:sha1:a9410cd1af7c1194fbda1457c74b8ab25547e1e6 Add riscv64{imac,gc}-unknown-none-elf targets Previous attempt by @fintelia: https://github.com/rust-lang/rust/pull/58012 Related: https://github.com/rust-embedded/wg/issues/218