summary refs log tree commit diff
path: root/.github
AgeCommit message (Collapse)AuthorLines
2023-07-08Rollup merge of #113173 - Kobzol:ci-concurrency-group-workflow, r=pietroalbiniMatthias Krüger-1/+1
CI: include workflow name in concurrency group Currently, this won't change anything, because we only have one relevant workflow (`CI`), but for future proofing we should probably include the workflow name in the concurrency group. Found by ``@klensy`` [here](https://github.com/rust-lang/rust/pull/113059#discussion_r1247213606).
2023-07-07Auto merge of #112796 - Kobzol:ci-merge-msvc-cargo-tools, r=pietroalbinibors-8/+3
CI: merge msvc cargo and tools jobs The `x86_64-msvc-cargo` and `x86_64-msvc-tools` jobs both run for ~1 hour, but most of that time is actually spent in building LLVM and `rustc`, so I want to try merging them. ![image](https://github.com/rust-lang/rust/assets/4539057/8652fa2a-b8b7-41d0-8f16-555d31acd9a5)
2023-07-06Auto merge of #112779 - Kobzol:ci-merge-llvm-14, r=pietroalbinibors-4/+1
CI: merge x86_64-gnu-llvm-14 and x86_64-gnu-llvm-14-stage1 CI jobs Another attempt to shorten CI job times. Suggested by `@the8472` [here](https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/CI.20usage/near/367172221).
2023-07-02Remove MIPS host CI workflowsJubilee Young-12/+0
2023-06-30CI: include workflow name in concurrency groupJakub Beránek-1/+1
Currently, this won't change anything, because we only have one relevant workflow (`CI`), but for future proofing we should probably include the workflow name in the concurrency group.
2023-06-29CI: do not cancel concurrent builds on the same branchJakub Beránek-1/+1
Add an exception for try and try-perf branches to enable concurrent try builds and unrolled rollup builds.
2023-06-26CI: do not cancel concurrent builds on the same branchJakub Beránek-1/+1
Instead, only cancel them if the builds have the same commit SHA.
2023-06-26Rollup merge of #112955 - Kobzol:ci-pr-cancel-workflows, r=Mark-SimulacrumMatthias Krüger-21/+3
CI: cancel in-progress workflow runs after a push Experimenting with the `concurrency` attribute. r? `@Mark-Simulacrum`
2023-06-25Remove `cancel-outdated` actionJakub Beránek-21/+0
2023-06-25CI: do not run Bump dependencies workflow on forksJakub Beránek-0/+3
2023-06-23issue template: add clippy entry which points to the clippy repoMatthias Krüger-0/+3
2023-06-23Cancel in-progress workflow runs after a pushJakub Beránek-0/+3
2023-06-19CI: merge `x86_64-msvc-cargo` and `x86_64-msvc-tools` jobsJakub Beránek-8/+3
2023-06-19CI: merge x86_64-gnu-llvm-14 and x86_64-gnu-llvm-14-stage1 CI jobsJakub Beránek-4/+1
2023-06-18Auto merge of #112645 - Kobzol:ci-mingw-merge, r=pietroalbinibors-18/+4
CI: merge `mingw` test CI jobs Same as https://github.com/rust-lang/rust/pull/112633, but for `mingw`. From the logs it looks like the runner spends 40 minutes compiling `rustc`, and then `10`/`20` minutes running tests. It seems wasteful to split that into two jobs. CI run: https://github.com/rust-lang/rust/actions/runs/5275702134/jobs/9541479343?pr=112645 r? `@jyn514`
2023-06-18Merge `mingw-1/2` CI jobsJakub Beránek-18/+4
2023-06-17Rollup merge of #110805 - pitaj:master, r=Mark-SimulacrumMatthias Krüger-0/+139
Github action to periodically `cargo update` to keep dependencies current Opens a PR periodically with the results of `cargo update`. If an unmerged PR for the branch `cargo_update` already exists, it will edit then reopen it if necessary. ~~This also uses [`cargo-upgrades`](https://gitlab.com/kornelski/cargo-upgrades) to provide a list of available major upgrades in the PR body.~~ It includes the list of changes output by `cargo update` in the commit message and PR body. Note that this output is currently sub-optimal due to https://github.com/rust-lang/cargo/issues/9408, but if updates are made more regularly that is less likely to show up. Example PR: https://github.com/pitaj/rust/pull/2 Example action run: https://github.com/pitaj/rust/actions/runs/5035731903 Prior discussion: https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/dependabot.20updates.3F Up for discussion: - What period do we want? Currently weekly - What user should it use? Currently "Github Actions" - Do we need the extra security of provided by executing `cargo update` and `cargo-upgrades` in a separate job? If not I can simplify it to not need artifacts. - PR message wording - PR should probably always be `rollup=always`? - What branch should it use? - What should it do if no updates are available? Currently fails the job on empty commit - Should the yml file live in `src/ci` instead of directly under workflows? - ~~Is using the latest nightly toolchain enough to ensure compatibility with `Cargo.lock` and `Cargo.toml`s in master?~~ Now pulls the bootstrap version from stage0.json r? infra
2023-06-17Auto merge of #112407 - tgross35:ci-docs-publish, r=Mark-Simulacrumbors-0/+36
Publish docs as github artifacts during CI Discussed here: https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/Building.20docs.20for.20PR.20CI The goal is to make docs available for download after CI runs on PRs, for easy review of API changes. Notes: - Currently this only captures library documentation (`core`, `alloc`, `std`, `test`, `proc_macro`) - You can't see artifacts until the entire workflow run has completed https://github.com/actions/upload-artifact/issues/53 - There is currently a generic file name `ci-artifacts`. No way to customize this based on contained files unfortunately https://github.com/actions/upload-artifact/issues/349 You can find the results at the bottom of the CI "summary" page: <img width="379" alt="image" src="https://github.com/rust-lang/rust/assets/13724985/d3748e59-242c-40f8-9f54-82177b9b481b">
2023-06-14Merge `msvc-1/2` CI jobsJakub Beránek-14/+4
2023-06-12Publish docs as github artifacts during CITrevor Gross-0/+36
This PR saves library docs as github artifacts so they can be easily viewed for review. Discussed in <https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/Building.20docs.20for.20PR.20CI>
2023-06-10run `cargo update` weeklyPeter Jaszkowiak-0/+139
- Keep Cargo.lock dependencies current - Presents output from `cargo update` in commit and PR - Edit existing open PR, otherwise open a new one - Skip if existing open PR is S-waiting-on-bors
2023-06-01Do not build components unneeded for perf bot in try buildsJakub Beránek-0/+1
2023-05-12ci: Add support for dist-loongarch64-linuxWANG Rui-0/+3
Co-Authored-By: YANG Xiaojuan <yangxiaojuan@loongson.cn>
2023-05-07Auto merge of #111224 - jyn514:default-tidy, r=pietroalbinibors-5/+1
Remove `tidy` key in PR CI This avoids confusing error messages when adding an `auto` job to CI (as recommended in the dev-guide: https://rustc-dev-guide.rust-lang.org/tests/ci.html#using-ci-to-test). cc https://rust-lang.zulipchat.com/#narrow/stream/182449-t-compiler.2Fhelp/topic/Do.20.60needs-profiler-support.60.20tests.20not.20run.20in.20CI.3F/near/355302998 r? `@ghost`
2023-05-06Auto merge of #110972 - ehuss:remove-awscli, r=pietroalbinibors-9/+3
Remove aws cli install. All runner images have the AWS CLI 2 installed, so there isn't a really strong reason to install our own version anymore. The version we were installing was 1.27.122. The runner images currently have 2.11.x (the exact version varies by image). I do not have the means to really test if the new version has any issues. I looked at all the `aws` commands, and none of them seem to be doing anything unusual. The page at https://docs.aws.amazon.com/cli/latest/userguide/cliv2-migration-changes.html contains a list of all the breaking changes, and I didn't see anything that looked important.
2023-05-04Remove `tidy` key in PR CIjyn-5/+1
This avoids confusing error messages when adding an `auto` job to CI (as recommended in the dev-guide: https://rustc-dev-guide.rust-lang.org/tests/ci.html#using-ci-to-test).
2023-05-03Auto merge of #110846 - jdno:reduce-builder-sizes, r=pietroalbinibors-7/+7
Optimize builder sizes The infra-team is continuously monitoring the efficiency of the CI system in an effort to improve overall build times and resource usage. Some builders have used much less than their allocated resources, so we are testing smaller builder sizes for them. r? `@pietroalbini`
2023-04-30Set the AWS region.Eric Huss-0/+3
2023-04-28Remove aws cli install.Eric Huss-9/+0
2023-04-26Downsize builders for some x86_64-gnu targetsJan David-4/+4
The infra-team is continuously monitoring the efficiency of the build system in an effort to improve overall build times and resource usage. The builders for some of the `x86_64-gnu` targets have used much less resources than allocated in the past, so we are testing a smaller builder size for them.
2023-04-26Downsize builder for mingw-checkJan David-1/+1
The infra-team is continuously monitoring the efficiency of the build system in an effort to improve overall build times and resource usage. The builder for the `mingw-check` target have used much less resources than allocated in the past, so we are testing a smaller builder size for it.
2023-04-26Downsize builders for i686-gnuJan David-2/+2
The infra-team is continuously monitoring the efficiency of the build system in an effort to improve overall build times and resource usage. The builders for the `i686-gnu` targets have used much less resources than allocated in the past, so we are testing a smaller builder size for them.
2023-04-25Use the standard macOS CI runnerRyan Levick-6/+6
2023-04-20Rollup merge of #110424 - jsoref:spelling-misc, r=Mark-SimulacrumYuki Okushi-2/+2
Spelling misc These two files seem to be fairly distinct from everything else. That said, if this project doesn't like changing changelogs, I'm happy to drop the changes to `RELEASES.md`
2023-04-17Spelling miscJosh Soref-2/+2
* environment * nonexistent * potential * prefixes * stabilization * suffixes * use Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
2023-04-16ci: add a runner for vanilla LLVM 16Josh Stone-0/+4
Like #107044, this will let us track compatibility with LLVM 16 going forward, especially after we eventually upgrade our own to the next. This also drops `tidy` here and in `x86_64-gnu-llvm-15`, syncing with that change in #106085.
2023-04-10Trim down core counts for fast buildersMark Rousskov-36/+36
These builders aren't particularly high on overall average CPU usage and finish in typically around 30 minutes. Cutting their core counts will hopefully not significantly increase wall-time while cutting costs, allowing us to shift some of the wins into our slower builders.
2023-04-02Improve job names in Github Actions previewjyn-3/+3
Before: `CI / PR (mingw-check, false, ubuntu-20.04-16core-64gb) (pull_request)` After: `CI / PR - mingw-check (pull_request)`
2023-03-19Move us to the new large runners poolMark Rousskov-62/+62
For now this keeps all the configuration identical (AFAICT) but we'll likely want to play with the specifics to move some of the slower builders to larger machines and the faster builders to smaller machines, likely reducing overall usage and improving CI times.
2023-03-13Revert "enable ThinLTO for rustc on x86_64-pc-windows-msvc dist builds"Nilstrieb-1/+1
This lead to a miscompilation in at least `char::is_whitespace` and probably in more unknown places..... This reverts commit 684663ed380d0e6a6e135aed9c6055ab4ba94ac8.
2023-02-22Re-apply "switch to the macos-12-xl builder"Michael Goulet-6/+6
This reverts commit e63ec2e1402eaff949e5c53b8f6062b152010fcc.
2023-02-10Update the minimum external LLVM to 14Josh Stone-6/+2
2023-02-08Rollup merge of #107773 - Mark-Simulacrum:rename-auto-template, r=estebankMatthias Krüger-1/+1
Clearly signal purpose of the yaml template Following up on https://github.com/rust-lang/rust/pull/106898#issuecomment-1383238532
2023-02-07Clearly signal purpose of the yaml templateMark Rousskov-1/+1
2023-02-05Run the tools builder on all PRsJoshua Nelson-2/+1
Previously, it would only run on changes to subtrees, submodules, or select directories. That made it so that changes to the compiler that broke tools would only be detected on a full bors merge. This makes it so the tools builder runs by default, making it easier to catch breaking changes to clippy (which was the most effected).
2023-02-03Auto merge of #107543 - ehuss:protocol-sparse, r=jyn514bors-0/+3
Enable Cargo's sparse protocol in CI This enables the sparse protocol in CI in order to exercise and dogfood it. This is intended test the production server in a real-world situation. Closes #107342
2023-02-01Auto merge of #107574 - compiler-errors:back-to-old-mac-builders-pls, ↵bors-6/+6
r=pietroalbini Revert "switch to the macos-12-xl builder" This reverts commit fcbae989ae790d5b9a0a23ceba242d0b0d4e6c5b. This should fix the bors failures in https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/Every.20rust-lang.2Frust.20PR.20is.20failing.20bors
2023-02-01Revert "switch to the macos-12-xl builder"Michael Goulet-6/+6
This reverts commit fcbae989ae790d5b9a0a23ceba242d0b0d4e6c5b.
2023-01-31Enable Cargo's sparse protocol in CIEric Huss-0/+3
2023-01-31Rollup merge of #106898 - estebank:ice-forms-are-a-headache, r=Mark-SimulacrumGuillaume Gomez-3/+52
Include both md and yaml ICE ticket templates * Existing compilers link to the md version * The YAML version field for the backtrace *doesn't let us paste a full backtrace* * We will need the YAML version in order to be able to submit reports once we start storing the backtrace to disk Follow up to #106831. Reaction to #106874, which made me realize that *really* long backtraces are rejected by GitHub Forms. A single backtrace won't hit this, but ICEs sometimes compound.
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-12 03:51:53 +0000