diff options
| author | bors <bors@rust-lang.org> | 2024-07-19 18:07:52 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-07-19 18:07:52 +0000 |
| commit | 057c4ae28766613da5b6578fa13d2412604b633b (patch) | |
| tree | bf7bfef7c9e2812ea80fb5870097a169157183ef /compiler/rustc_codegen_llvm/src/errors.rs | |
| parent | ac2ba15adda9f801092c58cf73ecc681cc2924fa (diff) | |
| parent | 8940bc3c46b5360024ba532a01067e76e3199dbe (diff) | |
| download | rust-057c4ae28766613da5b6578fa13d2412604b633b.tar.gz rust-057c4ae28766613da5b6578fa13d2412604b633b.zip | |
Auto merge of #13124 - xFrednet:00000-lintcheck-crates, r=Alexendoo
Lintcheck: Update crates and expand CI testset to 200 crates
This PR adds a new `ci_crates.toml` to lintcheck for our CI. The 200 crates take about 14 minutes, which is slightly more than the 10 I aimed for but still reasonable. The testset is constructed from:
* 5 crates that compile to binaries
* 4 crates that have been mentioned in ICE issues
* 1 crates "random" crates from `lintcheck_crates.toml`
* 190 crates from the top 200 crates from crates.io
During testing, I noticed a few panics in lintcheck. I've fixed them where possible, or at least improved the error message.
The new test set generates 500+ MB of json lints, which are compressed to a ~24mb artifact.
---
This PR also updates our `lintcheck_crates.toml`. I mainly updated the versions, removed some very outdated crates, and added some new ones. I targeted 25 crates as those are pretty fast to lint and a good precursor for our CI.
---
Optional TODO:
* It's likely that some crates are compiled several times. We could potentially safe some time, by using `--recursive` in our CI.
This is something I want to investigate, but it shouldn't be a blocker for this PR.
---
r? `@Alexendoo`
changelog: none
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/errors.rs')
0 files changed, 0 insertions, 0 deletions