Don't depend on crate names in tests/ui-fulldeps/missing-rustc-driver-error.rs

Not only are they a pain to update, but they differ depending on whether `parallel-rustc` is enabled or not
This commit is contained in:
jyn 2023-07-08 14:50:57 -05:00
parent 934e7e6c26
commit 30e34f3857
2 changed files with 3 additions and 13 deletions

View File

@ -1,8 +1,8 @@
// Test that we get the following hint when trying to use a compiler crate without rustc_driver.
// error-pattern: try adding `extern crate rustc_driver;` at the top level of this crate
// compile-flags: --emit link
// The exactly list of required crates depends on the target. as such only test Unix targets.
// only-unix
// normalize-stderr-test ".*crate .* required.*\n\n" -> ""
// normalize-stderr-test: "aborting due to [0-9]+" -> "aborting due to NUMBER"
#![feature(rustc_private)]

View File

@ -2,15 +2,5 @@ error: crate `rustc_serialize` required to be available in rlib format, but was
|
= help: try adding `extern crate rustc_driver;` at the top level of this crate
error: crate `smallvec` required to be available in rlib format, but was not found in this form
error: crate `thin_vec` required to be available in rlib format, but was not found in this form
error: crate `indexmap` required to be available in rlib format, but was not found in this form
error: crate `hashbrown` required to be available in rlib format, but was not found in this form
error: crate `equivalent` required to be available in rlib format, but was not found in this form
error: aborting due to 6 previous errors
error: aborting due to NUMBER previous errors