about summary refs log tree commit diff
path: root/tests/codegen/integer-overflow.rs
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2025-01-06 20:59:34 +0100
committerGitHub <noreply@github.com>2025-01-06 20:59:34 +0100
commitc31a4b9ac46a752d26b0fc9a56942eef16fe631c (patch)
tree3973a3d0f47fb05f4e2b5055323a2d70ce0a51e9 /tests/codegen/integer-overflow.rs
parent68791efa2961780361eba4d98cdf75608c2adacf (diff)
parent5298f85a0a2eadad45368137d57c1ff5a4adfd92 (diff)
downloadrust-c31a4b9ac46a752d26b0fc9a56942eef16fe631c.tar.gz
rust-c31a4b9ac46a752d26b0fc9a56942eef16fe631c.zip
Rollup merge of #135097 - Zalathar:coverage-test-step, r=Kobzol
bootstrap: Consolidate coverage test suite steps into a single step

Now that I have more understanding of bootstrap steps, and a renewed distaste for unnecessary macros, I have managed to express the subtleties of the `tests/coverage` test suite in a single step defined in ordinary code, with no need for helper macros.

Deciding which modes to run is still a bit clunky due to limitations in existing ShouldRun/PathSet APIs, but I think it's a net improvement over having to declare several different steps to handle the suite path and aliases.

The interaction with `--skip` isn't as nice as I'd like, but all of the known limitations are limitations that already existed in the previous implementation.

One minor change is that by default compiletest is now invoked in `coverage-run` mode even when cross-compiling. However, in that situation compiletest still knows that it should skip all of the individual coverage-run tests.

r? jieyouxu (or reassign)
Diffstat (limited to 'tests/codegen/integer-overflow.rs')
0 files changed, 0 insertions, 0 deletions