diff options
| author | Jacob Pratt <jacob@jhpratt.dev> | 2025-03-07 21:57:51 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-03-07 21:57:51 -0500 |
| commit | f1051ed6f105e73a7fff34a472ced9cf19c93f96 (patch) | |
| tree | 2e8f73ec8dace57841e29909085f2a77152731f9 /compiler/rustc_errors/src/snippet.rs | |
| parent | 8cf86cd68d5f3787f190933cac87e95d00618223 (diff) | |
| parent | d5da6b71fa7f29946a41d624e038c1c0eed8a4d3 (diff) | |
| download | rust-f1051ed6f105e73a7fff34a472ced9cf19c93f96.tar.gz rust-f1051ed6f105e73a7fff34a472ced9cf19c93f96.zip | |
Rollup merge of #138013 - Kobzol:ci-post-merge-analysis, r=marcoieni
Add post-merge analysis CI workflow This PR adds a post-merge analysis workflow, which was discussed [here](https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/Reporting.20test.20suite.20statistics.20after.20merge). The workflow currently analyzes test suite results from bootstrap metrics. It downloads metrics for all known jobs in the parent and current (HEAD) commit, compares them and prints a truncated diff. It then posts this diff to the merged PR as a comment. Later I also want to add other statistics to the analysis, e.g. changes in CI/bootstrap step durations. It can be tested locally e.g. using this: ``` cargo run --release --manifest-path src/ci/citool/Cargo.toml post-merge-report 3cb02729ab3c6583a3b1d1845c5e22b674f04b8d fd17deacce374a4185c882795be162e17b557050 ``` This uses a slightly older commit as a parent, to have more results in the diff (normally the diff won't be so large). CC `@jieyouxu` r? `@marcoieni`
Diffstat (limited to 'compiler/rustc_errors/src/snippet.rs')
0 files changed, 0 insertions, 0 deletions
