about summary refs log tree commit diff
path: root/.github
AgeCommit message (Collapse)AuthorLines
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
2025-03-15Refactor metrics generation stepJakub Beránek-2/+6
2025-03-15Rollup merge of #138454 - Kobzol:post-merge-workflow-fixes, r=jieyouxuLeón Orell Valerian Liehr-1/+6
Improve post-merge workflow Contains various fixes for the post-merge workflow implemented in https://github.com/rust-lang/rust/pull/138013, which were suggested on Zulip. This PR changes the grouping of test diffs and ignores doctests, as they are too noisy. I'll post an example output (before/after this PR) in comments below. r? ```@jieyouxu```
2025-03-13Print job doc URL on job failureJakub Beránek-2/+14
2025-03-13Output job doc URL to allow Rust Log Analyzer to access itJakub Beránek-0/+1
2025-03-13Collapse report in `<details>`Jakub Beránek-1/+6
2025-03-13Add note about the experimental statusJakub Beránek-1/+1
2025-03-11Fix post-merge workflow许杰友 Jieyou Xu (Joe)-1/+1
The command is called `post-merge-report` not `post-merge-analysis`.
2025-03-08Fix checkout in post-merge workflowJakub Beránek-0/+5
2025-03-08Add missing `GH_TOKEN` environment variableJakub Beránek-2/+3
It is needed for using the `gh` CLI commands.
2025-03-07Add post-merge analysis CI workflowJakub Beránek-0/+36
2025-03-05Upload Datadog average CPU usage metric in citoolJakub Beránek-6/+2
2025-03-05Make citool compilation fasterJakub Beránek-3/+3
2025-03-04Postprocess test suite metrics into GitHub summaryJakub Beránek-0/+17
2025-03-03Rollup merge of #137849 - jieyouxu:undo-workaround, r=KobzolMatthias Krüger-14/+0
Revert "Remove Win SDK 10.0.26100.0 from CI" Part of #137733. Resolves #137733. The remove-latest-windows-sdk workaround workaround should no longer be necessary, now that we bumped (1) cargo `cc` and (2) `rustc_{codegen_ssa,llvm}` `cc`. This reverts commit 25617c7e695d716d0ecb3cf2366d371441505e47, the remove-latest-windows-sdk workaround from #137753. try-job: i686-msvc-1 try-job: i686-msvc-2 try-job: dist-i686-msvc
2025-03-02Auto merge of #136864 - Kobzol:citool, r=marcoienibors-3/+6
Rewrite the `ci.py` script in Rust It would seem that I would learn by now that any script written in Python will become unmaintainable sooner or later, but alas.. r? `@marcoieni` try-job: aarch64-gnu try-job: dist-x86_64-linux-alt try-job: x86_64-msvc-ext2 Fixes: https://github.com/rust-lang/rust/issues/137013
2025-03-01Revert "Remove Win SDK 10.0.26100.0 from CI"许杰友 Jieyou Xu (Joe)-14/+0
This reverts commit 25617c7e695d716d0ecb3cf2366d371441505e47.
2025-02-28Remove Win SDK 10.0.26100.0 from CIChris Denton-0/+14
2025-02-20Auto merge of #137023 - Kobzol:bump-sccache, r=marcoienibors-0/+1
Bump sccache in CI to 0.9.1 We haven't updated the used sccache version for years, it has accrued a bunch of fixes and features in the meantime. It now supports the `--show-adv-stats` flag, which gives a more detailed summary of the results of caching. And it can also cache Rust code, which could be useful in the future (https://github.com/rust-lang/rust/pull/136942 - although now there are no large wins). It also supports caching PGO now, but since the PGO profiles are always different, it won't make any real difference. https://github.com/rust-lang/rust/pull/133076 previously tried to update the version to 0.3 (CC `@klensy)` r? `@marcoieni`
2025-02-17Test citool on CIJakub Beránek-0/+1
2025-02-17Update documentationJakub Beránek-2/+2
2025-02-17Use citool in CIJakub Beránek-3/+5
2025-02-14Add sccache S3 regionJakub Beránek-0/+1
2025-02-10Print the environment a second timeChris Denton-0/+5
2025-02-05Don't install msys2Chris Denton-19/+0
windows-msvc doesn't need it and windows-gnu has its own version
2025-01-21CI: free disk with in-tree script instead of GitHub ActionMarcoIeni-1/+1
Co-authored-by: whiteio <chriswhiteiodev@gmail.com>
2025-01-19Rollup merge of #135679 - onur-ozkan:bootstrap-issue-template, r=jieyouxuGuillaume Gomez-0/+70
create an issue template for bootstrap Resolves #135593 cc `@rust-lang/bootstrap`
2025-01-19create an issue template for bootstraponur-ozkan-0/+70
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-01-18Auto merge of #135682 - matthiaskrgr:rollup-cl7zlt1, r=matthiaskrgrbors-6/+17
Rollup of 7 pull requests Successful merges: - #133700 (const-eval: detect more pointers as definitely not-null) - #135290 (Encode constraints that hold at all points as logical edges in location-sensitive polonius) - #135478 (Run clippy for rustc_codegen_gcc on CI) - #135583 (Move `std::pipe::*` into `std::io`) - #135612 (Include x scripts in tarballs) - #135624 (ci: mirror buildkit image to ghcr) - #135661 (Stabilize `float_next_up_down`) r? `@ghost` `@rustbot` modify labels: rollup
2025-01-17ci: mirror buildkit image to ghcrMarcoIeni-6/+17
2025-01-17ci: improve github action nameMarcoIeni-1/+1
2025-01-16ci: mirror ubuntu:22.04 to ghcr.ioMarcoIeni-0/+57
2025-01-09CI: fix name of jobsJakub Beránek-3/+3
There is a difference between the `image` (the Dockerfile), the `name` of the job (which determines also its properties) and the `full_name`, which includes the `auto/try/pr` prefix.
2025-01-09Rollup merge of #134898 - Kobzol:ci-python-script, r=MarcoIeniMatthias Krüger-2/+2
Make it easier to run CI jobs locally This PR extends the Python CI script to perform a poor man's CI-like execution of a given CI job locally. It's not perfect, but it's better than nothing. r? `@jieyouxu`
2025-01-07Add a command to run a given Linux CI job locallyJakub Beránek-1/+1
2025-01-07Rename CI script from `calculate-job-matrix` to `ci.py`Jakub Beránek-2/+2
2025-01-07Remove workaround from pull request templateUrgau-1/+1
as triagebot/rustbot now ignores HTML blocks. cf. https://github.com/rust-lang/triagebot/pull/1869
2024-12-19ci: use ubuntu `24` instead of `latest`MarcoIeni-5/+5
2024-12-16Auto merge of #134095 - Kobzol:datadog-lockfile, r=MarcoIenibors-2/+3
[CI] Use a lockfile for installing the `datadog` package Without a lockfile, it could fail to compile when the dependencies have changed. Reported [here](https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/CI.20failure.20in.20DataDog.20upload). r? `@jdno` try-job: x86_64-msvc-ext2
2024-12-16[CI] Use a lockfile for installing the `datadog` packageJakub Beránek-2/+3
Without a lockfile, it could fail to compile when the dependencies have changed.
2024-12-09Configure renovatebotJakub Beránek-0/+14