summary refs log tree commit diff
path: root/src/tools/tidy
AgeCommit message (Collapse)AuthorLines
2024-08-31Rollup merge of #129816 - RalfJung:tidy-feature-issue-mismatch, ↵Matthias Krüger-1/+2
r=compiler-errors tidy: say which feature gate has a stability issue mismatch This gives some valuable context to what the error is actually about :)
2024-08-31Rollup merge of #129605 - jieyouxu:needs-llvm-components, r=Mark-SimulacrumMatthias Krüger-2/+8
Add missing `needs-llvm-components` directives for run-make tests that need target-specific codegen Without suitable `needs-llvm-components` directives, some run-make tests exercising target-specific codegen can fail if the LLVM used is built without the necessary components. Currently, the list is: ``` tests\run-make\print-target-list tests\run-make\print-to-output tests\run-make\print-cfg tests\run-make\target-without-atomic-cas ``` This PR also skips tidy checks for revisions and `needs-llvm-components` for run-make tests since revisions are not supported. Fixes #129390. Fixes #127895. cc ``@petrochenkov`` who noticed this, thanks! Would be great if you could confirm that this fixes the test errors for you locally.
2024-08-31tidy: say which feature gate has a stability issue mismatchRalf Jung-1/+2
2024-08-26Fix tidyMichael Goulet-4/+6
2024-08-26tidy: skip revision llvm-components check for run-make tests许杰友 Jieyou Xu (Joe)-2/+8
Since run-make tests do not support revisions.
2024-08-23Auto merge of #128507 - Oneirical:testart-from-scratch, r=jieyouxubors-1/+0
Migrate `libtest-thread-limit` `run-make` test to rmake Part of #121876 and the associated [Google Summer of Code project](https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html). Please try, but **only if normal CI is green**: // try-job: armhf-gnu // <- failed on this try-job: aarch64-gnu
2024-08-23rewrite libtest-thread-limit to rmakeOneirical-1/+0
2024-08-22rewrite x86_64-fortanix-unknown-sgx-lvi to rmakeOneirical-1/+0
2024-08-20skip updating when external binding is existedbohan-2/+1
2024-08-18Adjust licensing exceptions for WASM componentsTrevor Gross-7/+1
Recent versions of wasm-tools are now Apache-2.0 or MIT or Apache-2.0 with the LLVM exception, rather than strictly Apache-2.0 with the LLVM exception. The only component with the exception has moved to a new dependency `wasi-preview1-component-adapter-provider`.
2024-08-16rewrite reproducible-build to rmakeOneirical-1/+0
2024-08-15Rollup merge of #129037 - Zalathar:rmake-libtest, r=jieyouxuJubilee-2/+0
Port `run-make/libtest-json` and `run-make/libtest-junit` to rmake Unlike #126773, this is just a straightforward port to `rmake`, without attempting to switch to compiletest or get rid of the (trivial) Python scripts. Part of #121876. r? ````@jieyouxu```` try-job: x86_64-msvc try-job: i686-mingw try-job: test-various try-job: aarch64-gnu try-job: aarch64-apple
2024-08-15Rollup merge of #129018 - Oneirical:nmemonic-artifice, r=jieyouxuJubilee-2/+0
Migrate `rlib-format-packed-bundled-libs` and `native-link-modifier-bundle` `run-make` tests to rmake Part of #121876 and the associated [Google Summer of Code project](https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html). Please try: // try-job: test-various (ATTEMPTED: IGNORE RESTORED) try-job: x86_64-msvc try-job: aarch64-apple try-job: aarch64-gnu try-job: x86_64-mingw try-job: i686-mingw
2024-08-15Auto merge of #128787 - Oneirical:infohazardous-deprogram, r=jieyouxubors-3/+0
Coalesce `dep-info`, `dep-info-spaces` and `dep-info-doesnt-run-much` `run-make` tests into `dep-info` rmake.rs Part of #121876 and the associated [Google Summer of Code project](https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html). This is one of the most ancient tests in the `run-make` directory and its Makefile does some unexpected things, like creating and deleting a `done` directory over and over, sleeping at certain times (this is the [commit](https://github.com/rust-lang/rust/pull/13288/commits/0d9fd8e2a1f8aa43b4cf66272eaa3cf695bbdcd9) that added the `sleep`). I tried to preserve the intent of the test, which is smoke-testing that `dep-info` works. try-job: x86_64-msvc try-job: i686-mingw try-job: aarch64-gnu try-job: aarch64-apple try-job: test-various try-job: armhf-gnu try-job: dist-various-1
2024-08-15rewrite native-link-modifier-bundle to rmakeOneirical-1/+0
2024-08-15rewrite rlib-format-packed-bundled-libs to rmakeOneirical-1/+0
2024-08-15coalesce dep-info-spaces and dep-info-doesnt-run-much into dep-infoOneirical-3/+0
2024-08-14Auto merge of #128407 - Oneirical:feline-dotestication, r=jieyouxubors-2/+0
Migrate `min-global-align` and `no-alloc-shim` `run-make` tests to rmake Part of #121876 and the associated [Google Summer of Code project](https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html). Please try: try-job: aarch64-apple try-job: test-various try-job: armhf-gnu try-job: aarch64-gnu try-job: aarch64-gnu
2024-08-14rewrite no-alloc-shim to rmakeOneirical-1/+0
2024-08-14rewrite min-global-align to rmakeOneirical-1/+0
2024-08-14Rollup merge of #129071 - Zalathar:sysroot-unstable, r=jieyouxu许杰友 Jieyou Xu (Joe)-1/+0
Port `run-make/sysroot-crates-are-unstable` to rmake I already have a more elaborate draft at #126231 that tries to port the underlying Python script to rmake, but there's no need for the removal of Makefiles to be held up on complex tasks like that, so this PR simply takes the trivial Makefile and converts it into a trivial rmake recipe. Part of #121876. r? ``@jieyouxu``
2024-08-14Rollup merge of #128873 - ChrisDenton:windows-targets, r=Mark-SimulacrumMatthias Krüger-0/+1
Add windows-targets crate to std's sysroot With this PR, when backtrace is used as a crate from crates.io it will (once updated) use the real [windows-targets](https://crates.io/crates/windows-targets) crate. But when used from std it'll use std's replacement version. This allows sharing our customized `windows_tagets::link!` macro between std proper and the backtrace crate when used as part of std, ensuring a consistent linking story. This will be especially important once we move to using [`raw-dylib`](https://doc.rust-lang.org/reference/items/external-blocks.html#dylib-versus-raw-dylib) by default.
2024-08-14Port `run-make/sysroot-crates-are-unstable` to rmakeZalathar-1/+0
2024-08-13Port `run-make/libtest-junit` to rmakeZalathar-1/+0
2024-08-13Port `run-make/libtest-json` to rmakeZalathar-1/+0
2024-08-12rewrite remap-path-prefix-dwarf to rmakeOneirical-1/+0
2024-08-09Update tidy for new cranelift-bitset cratebjorn3-0/+2
2024-08-09Add windows-targets crate to std's sysrootChris Denton-0/+1
2024-08-08migrate `thumb-none-qemu` to rmakeFolkert-1/+0
2024-08-07Rollup merge of #128696 - Oneirical:second-linkage-rampage, r=jieyouxuMatthias Krüger-1/+0
Migrate `staticlib-dylib-linkage` `run-make` test to rmake Part of #121876 and the associated [Google Summer of Code project](https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html). I'm quite sure this has the same issue as the one brought up in [this discussion](https://github.com/rust-lang/rust/pull/128407#discussion_r1702439172), so I elected to keep the ignore MSVC. try-job: aarch64-apple try-job: x86_64-gnu-llvm-17 try-job: armhf-gnu
2024-08-07Rollup merge of #128636 - folkertdev:rmake-thumb-none-cortex-m, r=jieyouxuMatthias Krüger-1/+0
migrate `thumb-none-cortex-m` to rmake tracking issue: https://github.com/rust-lang/rust/issues/121876 I'll leave some comments/questions inline r? ```@jieyouxu``` try-job: armhf-gnu try-job: dist-various-1 try-job: test-various
2024-08-07rewrite pgo-indirect-call-promotion to rmakeOneirical-1/+0
2024-08-07rewrite pdb-buildinfo-cl-cmd to rmakeOneirical-1/+0
2024-08-07Rollup merge of #128757 - Oneirical:calm-before-the-sltorm, r=jieyouxuGuillaume Gomez-1/+0
Migrate `pgo-gen-lto` `run-make` test to rmake Part of #121876 and the associated [Google Summer of Code project](https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html). This one is so easy, I'm surprised I missed it. try-job: aarch64-apple try-job: x86_64-msvc try-job: x86_64-mingw try-job: i686-msvc try-job: i686-mingw try-job: x86_64-gnu-llvm-17
2024-08-07Rollup merge of #128700 - Oneirical:i-ffind-these-tests-quite-simdple, ↵Guillaume Gomez-1/+0
r=jieyouxu Migrate `simd-ffi` `run-make` test to rmake Part of #121876 and the associated [Google Summer of Code project](https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html). try-job: x86_64-msvc try-job: x86_64-mingw try-job: i686-msvc try-job: armhf-gnu try-job: test-various try-job: aarch64-apple try-job: x86_64-gnu-llvm-17
2024-08-07Auto merge of #128196 - Oneirical:poltergeist-manitestation, r=jieyouxubors-3/+0
Migrate `cross-lang-lto-upstream-rlibs`, `long-linker-command-lines` and `long-linker-command-lines-cmd-exe` `run-make` tests to rmake Part of #121876 and the associated [Google Summer of Code project](https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html). The `long-linker` tests are certainly doing something... interesting - they summon `rustc` calls with obscene quantities of arguments and check that this is appropriately handled. I removed the `RUSTC_ORIGINAL` magic - it's equivalent to `RUSTC` in `tools.mk`, so what is the purpose? Making it so the massive pile of flags doesn't modify rustc itself and start leaking into other tests? Tell me what you think. Please try: try-job: x86_64-msvc try-job: i686-msvc try-job: x86_64-mingw try-job: i686-mingw try-job: aarch64-apple try-job: test-various try-job: x86_64-gnu-debug try-job: x86_64-gnu-llvm-17
2024-08-06Rollup merge of #128107 - Oneirical:tomato-hartester, r=jieyouxuTrevor Gross-3/+0
Migrate `raw-dylib-alt-calling-convention`, `raw-dylib-c` and `redundant-libs` `run-make` tests to rmake Part of #121876 and the associated [Google Summer of Code project](https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html). Please try: // try-job: x86_64-msvc // try-job: x86_64-mingw // try-job: i686-msvc try-job: x86_64-gnu-llvm-17 try-job: aarch64-apple
2024-08-06rewrite pgo-gen-lto to rmakeOneirical-1/+0
2024-08-06rewrite long-linker-command-lines-cmd-exe to rmakeOneirical-1/+0
2024-08-06rewrite long-linker-command-lines to rmakeOneirical-1/+0
2024-08-06rewrite cross-lang-lto-upstream-rlibs to rmakeOneirical-1/+0
2024-08-06rewrite staticlib-dylib-linkage to rmakeOneirical-1/+0
2024-08-05rewrite simd-ffi to rmakeOneirical-1/+0
2024-08-05rewrite cdylib-dylib-linkage to rmakeOneirical-1/+0
2024-08-05rewrite redundant-libs to rmakeOneirical-1/+0
2024-08-05rewrite raw-dylib-c to rmakeOneirical-1/+0
2024-08-05rewrite raw-dylib-alt-calling-conventions to rmakeOneirical-1/+0
2024-08-05Auto merge of #127095 - Oneirical:testiary-education, r=jieyouxubors-2/+0
Migrate `reproducible-build-2` and `stable-symbol-names` `run-make` tests to rmake Part of #121876 and the associated [Google Summer of Code project](https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html). Needs try-jobs. try-job: x86_64-msvc try-job: armhf-gnu try-job: test-various try-job: aarch64-apple try-job: i686-msvc try-job: x86_64-mingw
2024-08-04Auto merge of #128534 - bjorn3:split_stdlib_workspace, r=Mark-Simulacrumbors-56/+64
Move the standard library to a separate workspace This ensures that the Cargo.lock packaged for it in the rust-src component is up-to-date, allowing rust-analyzer to run cargo metadata on the standard library even when the rust-src component is stored in a read-only location as is necessary for loading crates.io dependencies of the standard library. This also simplifies tidy's license check for runtime dependencies as it can now look at all entries in library/Cargo.lock without having to filter for just the dependencies of runtime crates. In addition this allows removing an exception in check_runtime_license_exceptions that was necessary due to the compiler enabling a feature on the object crate which pulls in a dependency not allowed for the standard library. While cargo workspaces normally enable dependencies of multiple targets to be reused, for the standard library we do not want this reusing to prevent conflicts between dependencies of the sysroot and of tools that are built using this sysroot. For this reason we already use an unstable cargo feature to ensure that any dependencies which would otherwise be shared get a different -Cmetadata argument as well as using separate build dirs. This doesn't change the situation around vendoring. We already have several cargo workspaces that need to be vendored. Adding another one doesn't change much. There are also no cargo profiles that are shared between the root workspace and the library workspace anyway, so it doesn't add any extra work when changing cargo profiles.
2024-08-04migrate `thumb-none-cortex-m` to rmakeFolkert-1/+0
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-13 20:29:29 +0000