about summary refs log tree commit diff
path: root/.github
AgeCommit message (Collapse)AuthorLines
2025-08-21ci: don't cleanup windows diskMarcoIeni-7/+2
2025-08-15Rollup merge of #145311 - marcoieni:clean-disk-in-background-windows, r=KobzolJakub Beránek-0/+5
ci: clean windows disk space in background
2025-08-14ci: clean windows disk space in backgroundMarcoIeni-0/+5
2025-08-12chore(ci): upgrade checkout to v5Rej Ect-7/+7
chore(ci): upgrade checkout to v5
2025-08-09improve "Documentation problem" issue template.binarycat-6/+6
rustdoc has its own issue template now, mention that. swap the order of the last two sentances so it reads more like a typical if/else chain (base case listed last). adjust some labels and descriptions
2025-07-31Rollup merge of #144053 - Kobzol:ci-remove-install-rust, r=marcoieniSamuel Tardieu-3/+0
Remove install Rust script from CI Windows ARM images should contain Rust now (https://github.com/actions/partner-runner-images/issues/77#issuecomment-3082613685). CC dpaoliello try-job: `*aarch64-msvc*`
2025-07-30Auto merge of #144305 - ChrisDenton:win-free-disk-space, r=marcoienibors-1/+8
Free disk space on Windows 2025 runners I've managed to reduce the time deletion takes by: - Using powershell, which is generally faster for filesystem operations than msys2 - Performing deletions concurrently then waiting for them all to complete It still takes 2-10 mins but that's not too bad.
2025-07-30Free disk space on Windows 2025 runnersChris Denton-1/+8
2025-07-21Remove spellcheck workflowJieyou Xu-23/+0
Unfortunately, the separate spellcheck GHA workflow does not really work with homu, if we would like to enforce the invariant that PR CI is a subset of Full CI (modulo carve outs). This is not prejudice against a reland of a `typos`-based spellcheck, it just probably has to go through the "usual" CI flow with bootstrap, so that it can work with homu.
2025-07-19Initialize mingw for the runner's userChris Denton-5/+0
2025-07-17Remove install Rust script from CIJakub Beránek-3/+0
Windows ARM images should contain Rust now.
2025-07-16Ensure home directory existsChris Denton-0/+5
This works around a missing mingw home directory in CI
2025-07-10Rollup merge of #140136 - dpaoliello:arm64winci, r=KobzolTrevor Gross-0/+3
Add an aarch64-msvc build running on ARM64 Windows Resurrecting rust-lang/rust#126341 Per <https://github.com/rust-lang/rfcs/pull/3817> we intend to promote `aarch64-pc-windows-msvc` to Tier 1. As part of that work, we are adding a pre-merge CI job to validate that changes do not break this target. Additionally, for consistency, the `dist-aarch64-msvc` job will also be run on Arm64 Windows runners. r? ``@Kobzol`` try-job: `*aarch64-msvc*`
2025-07-07Fix missing words in future tracking issueEric Huss-2/+2
Fixes some sloppy editing on my part.
2025-07-05Rollup merge of #143386 - clubby789:dep-bump-me, r=compiler-errorsMatthias Krüger-0/+1
Assign dependency bump PRs to me These PRs sometimes get lost as GH reduces their visibility, so I wanted to get an assignment so I can help these PRs land
2025-07-04Assign dependency bump PRs to meclubby789-0/+1
2025-07-03Rollup merge of #134006 - klensy:typos, r=nnethercoteJana Dönszelmann-0/+23
setup typos check in CI This allows to check typos in CI, currently for compiler only (to reduce commit size with fixes). With current setup, exclude list is quite short, so it worth trying? Also includes commits with actual typo fixes. MCP: https://github.com/rust-lang/compiler-team/issues/817 typos check currently turned for: * ./compiler * ./library * ./src/bootstrap * ./src/librustdoc After merging, PRs which enables checks for other crates (tools) can be implemented too. Found typos will **not break** other jobs immediately: (tests, building compiler for perf run). Job will be marked as red on completion in ~ 20 secs, so you will not forget to fix it whenever you want, before merging pr. Check typos: `python x.py test tidy --extra-checks=spellcheck` Apply typo fixes: `python x.py test tidy --extra-checks=spellcheck:fix` (in case if there only 1 suggestion of each typo) Current fail in this pr is expected and shows how typo errors emitted. Commit with error will be removed after r+.
2025-07-03setup CI and tidy to use typos for spellchecking and fix few typosklensy-0/+23
2025-07-02Rename mingw-check-tidy to tidyChris Denton-2/+2
2025-07-01Rename mingw-* CI jobs to pr-*Chris Denton-2/+2
2025-06-26Remove workflow run on masterJakub Beránek-4/+0
2025-06-26Remove cache for citoolJakub Beránek-7/+0
2025-06-19add issue template for rustdocbinarycat-0/+54
2025-06-13DRAFT: Add an aarch64-msvc build running on ARM64 WindowsDaniel Paoliello-0/+3
2025-06-10Only run `citool` tests on the `auto` branchJakub Beránek-1/+7
2025-06-09Run `calculate_matrix` job on the `master` branchJakub Beránek-0/+4
This allows us to reuse its cache on PR CI jobs.
2025-05-30ci: use arm to calculate job matrixMarcoIeni-1/+1
2025-05-29Provide secrets to try builds with new borsJakub Beránek-2/+2
2025-05-27Fix CI for unrolled builds on the `try-perf` branchJakub Beránek-7/+6
That branch is essentially the same as the `try` branch, it also needs S3 permissions. Long term, we should move rollup unrolling from rustc-perf to bors, so that we can have only a single try branch.
2025-05-22ci: prepare aws access keys for migrationMarcoIeni-4/+4
2025-05-21Add bors environment to CIJakub Beránek-0/+9
This will be used to access secrets once we move off rust-lang-ci.
2025-05-11Add an issue template for future-incompatible lintsEric Huss-0/+54
2025-05-06Handle PR not found in post-merge workflowJakub Beránek-0/+7
2025-04-25Rollup merge of #140148 - marcoieni:ci-aws-codebuild, r=KobzolMatthias Krüger-0/+13
CI: use aws codebuild for job dist-arm-linux try-job: dist-arm-linux
2025-04-23CI: use aws codebuild for job dist-arm-linuxMarcoIeni-0/+13
2025-04-20Remove `setup-upstream-remote.sh` and upstream handling.Jakub Beránek-3/+0
It shouldn't be needed anymore.
2025-04-15Use `rust-cache` to speed-up `citool` compilationJakub Beránek-0/+7
2025-04-09Tracking issue template: fine-grained information on style update statusJosh Triplett-1/+4
Inspired by some of the communication issues around the stabilization of `let`-chains, give more fine-grained information about the status of updating style for any new syntax. This does not change the process or blockers in any way; it only *documents* the current state in the tracking issue. For instance, in the case of `let`-chains, we would have checked the boxes for "Style team decision" and "(non-blocking) Formatting has been implemented", and not checked the box for the style guide. That would have then provided better supporting information for any decisions.
2025-04-08Rollup merge of #139547 - joshtriplett:library-tracking-issue-template, ↵Matthias Krüger-1/+3
r=Amanieu Update library tracking issue template to set S-tracking-unimplemented This will help people notice the `S-tracking-*` labels, and if the tracking issue *is* implemented, they can change the label. Discussed in a `@rust-lang/libs-api` meeting. r? `@Amanieu`
2025-04-08Update library tracking issue template to set S-tracking-unimplementedJosh Triplett-1/+3
This will help people notice the `S-tracking-*` labels, and if the tracking issue *is* implemented, they can change the label.
2025-03-27Add CI metadata to bootstrap metricsJakub Beránek-0/+2
This will allow us to provide links to CI workflows, jobs and summaries in the post-merge analysis report.
2025-03-19Rollup merge of #138658 - marcoieni:mirror-alpine-and-centos, r=KobzolMatthias Krüger-0/+7
CI: mirror alpine and centos images to ghcr
2025-03-18CI: mirror alpine and centos images to ghcrMarcoIeni-0/+7
2025-03-18Remove double nesting in post-merge workflowJakub Beránek-4/+3
2025-03-17Rollup merge of #138531 - Kobzol:test-diff-try-build, r=marcoieniMatthias Krüger-2/+17
Store test diffs in job summaries and improve analysis formatting This PR stores the test diffs that we already have in the post-merge workflow also into individual job summaries. This makes it easier to compare test (and later also other) diffs per job, which will be especially useful for try jobs, so that we can actually see the test diffs *before* we merge a given PR. As a drive-by, I also made a bunch of cleanups in `citool` and in the formatting of the summary and post-merge analyses. These changes are split into self-contained commits. The analysis can be tested locally with the following command: ```bash $ curl https://ci-artifacts.rust-lang.org/rustc-builds/<current-sha>/metrics-<job-name>.json > metrics.json $ cargo run --manifest-path src/ci/citool/Cargo.toml postprocess-metrics metrics.json --job-name <job-name> --parent <parent-sha> > out.md ``` For example, for [this PR](https://github.com/rust-lang/rust/pull/138523): ```bash $ curl https://ci-artifacts.rust-lang.org/rustc-builds/282865097d138c7f0f7a7566db5b761312dd145c/metrics-aarch64-gnu.json > metrics.json $ cargo run --manifest-path src/ci/citool/Cargo.toml postprocess-metrics metrics.json --job-name aarch64-gnu --parent d9e5539a39192028a7b15ae596a8685017faecee > out.md ``` Best reviewed commit by commit. r? `@marcoieni` try-job: aarch64-gnu try-job: dist-x86_64-linux
2025-03-17Small review improvementsJakub Beránek-2/+2
2025-03-17change config.toml to bootstrap.toml for bootstrap modulebit-aloo-1/+1
2025-03-15Print test diffs into GitHub summaryJakub Beránek-0/+5
So that we can also observe them for try builds, before merging a PR.
2025-03-15Print metrics postprocessing to stdoutJakub Beránek-1/+1
This allows the code to be simplified a little bit.
2025-03-15Do not fail the build if metrics postprocessing or DataDog upload failsJakub Beránek-0/+6