rust/src/ci/docker/scripts, branch stable https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=stable 2025-07-15T14:23:15+00:00 Fix handling of SCRIPT_ARG in docker images 2025-07-15T14:23:15+00:00 Nikita Popov npopov@redhat.com 2025-07-15T13:33:32+00:00 urn:sha1:4b421d44e20351426cf4ded11248bd1d0af40b5f Instead of making this a build parameter, pass the SCRIPT as an environment variable. To this purpose, normalize on always referring to a script in `/scripts`. For i686-gnu-nopt-2 I had to create a separate script, because Docker seems to be really terrible at command line argument parsing, so it's not possible to pass an environment variable that contains whitespace. Get rid of build-powerpc64le-toolchain.sh 2025-07-04T08:46:12+00:00 Jens Reidel adrian@travitia.xyz 2025-07-04T08:46:05+00:00 urn:sha1:12bc4096dcb81cb795fed68eeea3c36590befa25 The dist-powerpc64le-linux-musl runner never actually used the toolchain that the script produced, it instead used the one from crosstool-ng. The dist-powerpc64le-linux-gnu runner did use it, from what I can tell mainly to get a glibc 2.17 version with ppc64le support backported. Since crosstool-ng has the necessary patches, we can just use crosstool-ng to get an appropriate toolchain. While at it, use kernel 3.10 headers since that's the version documented in platform support for this target. Signed-off-by: Jens Reidel <adrian@travitia.xyz> Remove `build --stage 0` from CI scripts 2025-06-23T08:11:01+00:00 Jakub Beránek berykubik@gmail.com 2025-06-16T15:27:09+00:00 urn:sha1:809f75058e891b682c9a6f185de805b7f0a234e3 CI: rfl: move job forward to Linux v6.16-rc1 2025-06-08T19:37:37+00:00 Miguel Ojeda ojeda@kernel.org 2025-06-08T19:37:25+00:00 urn:sha1:f4ba1746cc1b13eb73f3739a5ff5e64cde56f078 Remove the comment on top as well, since that issue is now fixed in this new tag. Signed-off-by: Miguel Ojeda <ojeda@kernel.org> build dist for x86_64-pc-solaris and sparcv9-sun-solaris 2025-05-30T09:18:31+00:00 Petr Sumbera sumbera@volny.cz 2025-03-04T12:19:22+00:00 urn:sha1:0f1579b4bb21af7a79331a1a26dc2370ec182fc4 ci: move tests from x86_64-gnu-llvm-19 job to aarch64 2025-05-26T20:27:20+00:00 MarcoIeni 11428655+MarcoIeni@users.noreply.github.com 2025-05-26T20:27:20+00:00 urn:sha1:1b7a927d846ae02c3a403be0eb47714c557c49b4 Remove #![feature(let_chains)] from libcore 2025-05-23T00:47:43+00:00 est31 MTest31@outlook.com 2025-05-22T23:53:54+00:00 urn:sha1:6d716743211c1c7e28f32c48f586fbeb3068304f ci: split powerpc64le-linux job 2025-05-20T13:16:29+00:00 MarcoIeni 11428655+MarcoIeni@users.noreply.github.com 2025-05-20T13:16:29+00:00 urn:sha1:a8173fcd1f44baf1ef2f582983f17898317ff81b CI: rfl: move job forward to Linux v6.15-rc4 2025-04-29T15:40:17+00:00 Miguel Ojeda ojeda@kernel.org 2025-04-01T18:53:48+00:00 urn:sha1:6e267622240771b72ce76030072c1e3c02bf80df Signed-off-by: Miguel Ojeda <ojeda@kernel.org> Remove the `add_dummy_commit.sh` hack 2025-04-20T07:35:39+00:00 Jakub Beránek berykubik@gmail.com 2025-03-21T21:32:23+00:00 urn:sha1:432c4a80e9b03505f73e85828bd152a5efc2f98b The new git tests should be enough to check this scenario. We should ideally not be creating dummy commits on CI.