compiletest-rs icon indicating copy to clipboard operation
compiletest-rs copied to clipboard

An extraction of the compiletest utility from the Rust compiler

Results 37 compiletest-rs issues
Sort by recently updated
recently updated
newest added

This would have helped me to understand a broken configuration more quickly. I had compiletest set up to look for a couple of directories, but one was missing and it...

running `cargo test -- --nocapture` or `env RUST_TEST_NOCAPTURE=1 cargo test` does not output anything printed with `println!` if the test succeeds. If I make the test fail, it prints both...

This crate likely also suffers from https://github.com/rust-lang/rust/issues/5253, which got fixed by https://github.com/rust-lang/rust/pull/53196/commits/fe28bcf1db02afe184e3677ee034b2a5804f2466.

See https://travis-ci.org/Robbepop/string-interner/jobs/339735884 for the build log (`config.link_deps()`). And https://travis-ci.org/Robbepop/string-interner/jobs/339733480 for an earlier one (`config.target_ruscflags = Some("-L target/debug/deps"`). Locally on my Windows machine, `config.link_deps()` fails due to #81 and `config.target_rustcflags =...

When multi-span messages are emitted, the compiler duplicates the message in the JSON output for each span. Compiletest recognizes the first message, and reports mismatch for the rest.

Currently it fails to pick up correct error messages: ``` ---- [compile-fail] compile-fail/str_ref_deser.rs stdout ---- error: expected error: on line 6 not found: Serde does not support deserializing fields of...

Can compiletest-rs benchmark compilation? How would this work? Use case: I think at some point it may be useful to benchmark our lints at rust-clippy to see bottlenecks.