diff options
| author | Samuel Tardieu <sam@rfc1149.net> | 2025-08-26 23:25:01 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-08-26 23:25:01 +0200 |
| commit | a4924f01323763d5a652b8958a2f47622376f75d (patch) | |
| tree | 8617760588223cd3c7c7b46546e52e4a1f2c20f0 /compiler/rustc_span/src | |
| parent | 91ee6a4057ce4bf1ab6d2f932cae497488d67c81 (diff) | |
| parent | 9637774e328b7fb57cff80a94ed635ef234945a6 (diff) | |
| download | rust-a4924f01323763d5a652b8958a2f47622376f75d.tar.gz rust-a4924f01323763d5a652b8958a2f47622376f75d.zip | |
Rollup merge of #144499 - Enselic:ci-debuginfo-level-tests, r=davidtwco
ci: Begin running ui tests with `rust.debuginfo-level-tests=1` To reduce risk of regressing on generating debuginfo e.g. in the form of ICE:s. This will also ensure that future ui tests work with different debuginfo levels. See https://github.com/rust-lang/rust/issues/61117. When I looked at run time for different CI jobs, **x86_64-gnu-debug** was far from the bottleneck, so it should be fine to make it perform more work. A handful of tests are failing so we need to force debuginfo=0 on those for now. We'll start small with debuginfo=1. We'll step up to debuginfo=2 once most (all?) tests can handle debuginfo=1. There are more failures with debuginfo=2 than with debuginfo=1.
Diffstat (limited to 'compiler/rustc_span/src')
0 files changed, 0 insertions, 0 deletions