diff options
| author | Stuart Cook <Zalathar@users.noreply.github.com> | 2024-09-12 20:37:18 +1000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-09-12 20:37:18 +1000 |
| commit | 458a57adeba49fb5b9dcf379e96622ff93b567e0 (patch) | |
| tree | 62bda06672e90fc12422db8b5abca28480576665 /compiler/rustc_resolve/src | |
| parent | a3d9d13d7aba7bd35e79ad3cd9cb6cca9264329c (diff) | |
| parent | ed9b2bac36d93cdc8532f6bb86b9b8591f0a79e1 (diff) | |
| download | rust-458a57adeba49fb5b9dcf379e96622ff93b567e0.tar.gz rust-458a57adeba49fb5b9dcf379e96622ff93b567e0.zip | |
Rollup merge of #130256 - Zalathar:dump-stamp, r=jieyouxu
Re-run coverage tests if `coverage-dump` was modified If the `coverage-dump` tool was modified, coverage tests should not be treated as up-to-date, because the tool's output might have changed. Bootstrap already handles rebuilding the tool itself if its sources were changed, so all compiletest needs to do here is include the binary in the list of files whose timestamps are checked. This should have no effect on non-coverage tests, because bootstrap won't pass the `--coverage-dump-path` flag, so the path in compiletest's config will be None.
Diffstat (limited to 'compiler/rustc_resolve/src')
0 files changed, 0 insertions, 0 deletions