about summary refs log tree commit diff
path: root/src/ci/github-actions
AgeCommit message (Collapse)AuthorLines
2020-08-02Auto merge of #74675 - pietroalbini:aarch64-ci-fallible, r=Mark-Simulacrumbors-0/+10
Add fallible AArch64 CI builder This adds the `aarch64-gnu` CI builder to the `auto-fallible` job, as a first step in the process of actually gating on it. r? @Mark-Simulacrum
2020-07-28Use --stage 2 in checktoolsJoshua Nelson-1/+1
- Remove useless --stage 2 argument to checktools.sh - Fix help text for expand-yaml-anchors (it had a typo)
2020-07-27Use --stage 2 explicitly in CIJoshua Nelson-3/+3
- expand yaml anchors - don't use --stage 2 for dist; that's already the default
2020-07-23ci: add aarch64-gnu as a fallible auto builderPietro Albini-0/+10
2020-07-22Enable perf try builderMark Rousskov-3/+4
This adds a dedicated branch for perf to use for CI, intended to allow perf to enqueue builds without needing to use bors. bors is great, but bors requires an open PR to work, and we want to invoke perf on closed PRs sometimes (in particular, rollups).
2020-07-20ci: upload non-macOS from GHA instead of Azure PipelinesPietro Albini-4/+19
2020-07-20ci: allow RLA to pick the right PR numberPietro Albini-0/+9
2020-07-17ci: Replace exec-with-shell wrapper with "plain bash"Kristofer Rye-15/+4
Also, promote defaults.run.shell from inside only the primary jobs to the top level. The src/ci/exec-with-shell.py wrapper script was formerly used to change out the shell mid-job by intercepting a CI_OVERRIDE_SHELL environment variable. Now, instead, we just set `bash` as the global default across all jobs, and we also delete the exec-with-shell.py script. Signed-off-by: Kristofer Rye <kristofer.rye@gmail.com>
2020-07-16ci: Set `shell: bash` as a default, remove duplicatesKristofer Rye-20/+3
A follow-up to #74406, this commit merely removes the `shell: bash` lines where they are explicitly added in favor of setting defaults for *all* "run" steps. Signed-off-by: Kristofer Rye <kristofer.rye@gmail.com>
2020-07-16Set shell for github actions CIMark Rousskov-0/+20
2020-07-15Rollup merge of #72973 - msizanoen1:riscv-host, r=pietroalbiniManish Goregaokar-0/+3
RISC-V GNU/Linux as host platform This PR add a new builder named `dist-riscv64-linux` that builds the compiler toolchain for RISC-V 64-bit GNU/Linux. r? @alexcrichton
2020-07-15Auto merge of #71272 - jclulow:illumos-x86-ci, r=pietroalbinibors-0/+3
build dist for x86_64-unknown-illumos This change creates a new Docker image, "dist-x86_64-illumos", and sets things up to build the full set of "dist" packages for illumos hosts, so that illumos users can use "rustup" to install packages. It also adjusts the manifest builder to expect complete toolchains for this platform.
2020-07-11RISC-V GNU/Linux as host platformmsizanoen1-0/+3
2020-07-10ci: allow gating gha on everything but macOSPietro Albini-36/+45
In our GitHub Actions setup macOS is too unreliable to gate on it, but the other builders work fine. This commit splits the macOS builders into a separate job (called auto-fallible), allowing us to gate on the auto job without failing due to macOS spurious failures.
2020-07-08build dist for x86_64-unknown-illumosJoshua M. Clulow-0/+3
This change creates a new Docker image, "dist-x86_64-illumos", and sets things up to build the full set of "dist" packages for illumos hosts, so that illumos users can use "rustup" to install packages. It also adjusts the manifest builder to expect complete toolchains for this platform.
2020-07-03ci: move all x86_64 runners to the host-x86_64 directoryPietro Albini-1/+1
We need to add runners designed for an aarch64 host system, and it'd be nice to return an error message if someone tries to run an image designed for an host architecture in another one. To start the work on this, this commit moves all the existing builders in the host-x86_64 directory, and changes the run.sh script to look up the image in the correct directory based on the host architecture.
2020-07-01Rollup merge of #72569 - ChrisDenton:remove-innosetup, r=nikomatsakisManish Goregaokar-4/+0
Remove legacy InnoSetup GUI installer On Windows the InnoSetup `.exe` installer was superseded by the MSI installer long ago. It's no longer needed. The `.exe` installer hasn't been linked from the [other installation methods](https://forge.rust-lang.org/infra/other-installation-methods.html#standalone) page in many years. As far as I can tell the intent was always to remove this installer once the MSI proved itself. Though admittedly both installers feel very "legacy" at this point. Removing this would mean we only maintain one Windows GUI installer and would speed up the distribution phase. As a result of removing InnoSetup, this closes #24397
2020-06-29Revert "ci: allow gating gha on everything but macOS"Pietro Albini-45/+36
This reverts commit 8bc3122311dd70eabb0020e67e850b2b7904d972.
2020-06-20Auto merge of #73563 - Manishearth:rollup-oowgwwm, r=Manishearthbors-36/+45
Rollup of 9 pull requests Successful merges: - #72456 (Try to suggest dereferences on trait selection failed) - #72788 (Projection bound validation) - #72790 (core/time: Add Duration methods for zero) - #73227 (Allow multiple `asm!` options groups and report an error on duplicate options) - #73287 (lint: normalize projections using opaque types) - #73291 (Pre-compute `LocalDefId` <-> `HirId` mappings and remove `NodeId` <-> `HirId` conversion APIs) - #73378 (Remove use of specialization from librustc_arena) - #73411 (Update bootstrap to rustc 1.45.0-beta.2 (1dc0f6d8e 2020-06-15)) - #73443 (ci: allow gating GHA on everything but macOS) Failed merges: r? @ghost
2020-06-20Rollup merge of #73443 - pietroalbini:gha-auto-fallible, r=Mark-SimulacrumManish Goregaokar-36/+45
ci: allow gating GHA on everything but macOS In our GitHub Actions setup macOS is too unreliable to gate on it, but the other builders work fine. This commit splits the macOS builders into a separate job (called `auto-fallible`), allowing us to gate on the auto job without failing due to macOS spurious failures. cc https://github.com/rust-lang/rust-central-station/issues/848 r? @Mark-Simulacrum
2020-06-17ci: disable alt build during try buildsPietro Albini-5/+0
The build is not actually needed often, and it can be added back on a case-by-case basis if a specific PR needs access to it.
2020-06-15ci: allow gating gha on everything but macOSPietro Albini-36/+45
In our GitHub Actions setup macOS is too unreliable to gate on it, but the other builders work fine. This commit splits the macOS builders into a separate job (called auto-fallible), allowing us to gate on the auto job without failing due to macOS spurious failures.
2020-06-15Rollup merge of #73296 - ehuss:remove-msvc-aux, r=Mark-SimulacrumRalf Jung-6/+0
Remove vestigial CI job msvc-aux. This CI job isn't really doing anything, so it seems prudent to remove it. For some history: * This was introduced in #48809 when the msvc job was split in two to keep it under 2 hours (oh the good old days). At the time, this check-aux job did a bunch of things: * tidy * src/test/pretty * src/test/run-pass/pretty * src/test/run-fail/pretty * src/test/run-pass-valgrind/pretty * src/test/run-pass-fulldeps/pretty * src/test/run-fail-fulldeps/pretty * Tidy was removed in #60777. * run-pass and run-pass-fulldeps moved to UI in #63029 * src/test/pretty removed in #58140 * src/test/run-fail moved to UI in #71185 * run-fail-fulldeps removed in #51285 Over time through attrition, the job was left with one lonely thing: `src/test/run-pass-valgrind/pretty`. And of course, this wasn't actually running the "pretty" tests. The normal `run-pass-valgrind` tests ran, and then when it tried to run in "pretty" mode, all the tests were ignored because compiletest thought nothing had changed (apparently compiletest isn't fingerprinting the mode? Needs more investigation…). `run-pass-valgrind` is already being run as part of `x86_64-msvc-1`, so there's no need to run it here. I've taken the liberty of removing `src/test/run-pass-valgrind/pretty` as a distinct test. I'm guessing from the other PR's that the pretty tests should now live in `src/test/pretty`, and that the team has moved away from doing pretty tests on other parts of the `src/test` tree.
2020-06-12Remove vestigial CI job msvc-aux.Eric Huss-6/+0
2020-06-11Use preinstalled MSYS2Mateusz Mikuła-4/+0
2020-06-04Enable lld for Cargo tests on Windows.Eric Huss-1/+1
2020-05-25Remove legacy InnoSetup GUI installerChris Denton-4/+0
On Windows the InnoSetup installer was superseded by the MSI installer. It's no longer needed.
2020-05-11Configure cache domain for GHAMark Rousskov-0/+2
2020-04-29ci: use bash when executing the "bors build finished" jobsPietro Albini-0/+2
We don't clone the repository in those builders, so the default shell (src/ci/exec-with-shell.py) is not present there.
2020-04-22ci: remove duplicated job names on GHAPietro Albini-65/+0
2020-04-22ci: set a default shell on GHAPietro Albini-37/+37
2020-04-14Update the minimum external LLVM to 8Josh Stone-4/+4
LLVM 8 was released on March 20, 2019, over a year ago.
2020-03-31ci: disable cancel-outdated-builds for the try branchPietro Albini-0/+1
While for auto, try and PR builds we only want the latest commit to be tested, that's not true for try builds: each commit pushed to the branch is a different PR being tested, and we want multiple PRs to be tested in parallel if there is enough demand. Fixes #70569
2020-03-24ci: run the "bors build finished" jobs only during try and auto runsPietro Albini-2/+4
2020-03-24ci: run gha workflows for try, auto and master on the forkPietro Albini-3/+3
2020-03-24ci: add github actions configurationPietro Albini-0/+707
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-01-12 23:15:58 +0000