Use check-run-results for run-fail test stderr

Author: clubby789

src/tools/tidy/src/ui_tests.rs

@@ -17,7 +17,7 @@ use ignore::Walk;
 const ENTRY_LIMIT: u32 = 901;
 // FIXME: The following limits should be reduced eventually.
 
-const ISSUES_ENTRY_LIMIT: u32 = 1672;
+const ISSUES_ENTRY_LIMIT: u32 = 1684;
 
 const EXPECTED_TEST_FILE_EXTENSIONS: &[&str] = &[
     "rs",     // test source files

tests/ui/array-slice-vec/bounds-check-no-overflow.rs

@@ -1,5 +1,5 @@
 //@ run-fail
-//@ error-pattern:index out of bounds
+//@ check-run-results:index out of bounds
 //@ ignore-emscripten no processes
 
 use std::mem::size_of;

tests/ui/array-slice-vec/bounds-check-no-overflow.run.stderr

@@ -0,0 +1,3 @@
+thread 'main' panicked at $DIR/bounds-check-no-overflow.rs:9:5:
+index out of bounds: the len is 3 but the index is 2305843009213693952
+note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

tests/ui/array-slice-vec/dst-raw-slice.rs

@@ -1,7 +1,7 @@
 // Test bounds checking for DST raw slices
 
 //@ run-fail
-//@ error-pattern:index out of bounds
+//@ check-run-results:index out of bounds
 //@ ignore-emscripten no processes
 
 #[allow(unconditional_panic)]

tests/ui/array-slice-vec/dst-raw-slice.run.stderr

@@ -0,0 +1,3 @@
+thread 'main' panicked at $DIR/dst-raw-slice.rs:11:18:
+index out of bounds: the len is 3 but the index is 3
+note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

tests/ui/array-slice-vec/vec-overrun.rs

@@ -1,5 +1,5 @@
 //@ run-fail
-//@ error-pattern:index out of bounds: the len is 1 but the index is 2
+//@ check-run-results:index out of bounds: the len is 1 but the index is 2
 //@ ignore-emscripten no processes
 
 fn main() {

tests/ui/array-slice-vec/vec-overrun.run.stderr

@@ -0,0 +1,3 @@
+thread 'main' panicked at $DIR/vec-overrun.rs:11:17:
+index out of bounds: the len is 1 but the index is 2
+note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

tests/ui/async-await/issues/issue-65419/issue-65419-async-fn-resume-after-completion.rs

@@ -2,8 +2,8 @@
 // be talking about `async fn`s instead.
 
 //@ run-fail
-//@ error-pattern: thread 'main' panicked
-//@ error-pattern: `async fn` resumed after completion
+//@ check-run-results: thread 'main' panicked
+//@ check-run-results: `async fn` resumed after completion
 //@ edition:2018
 
 #![feature(coroutines, coroutine_trait)]

tests/ui/async-await/issues/issue-65419/issue-65419-async-fn-resume-after-completion.run.stderr

@@ -0,0 +1,3 @@
+thread 'main' panicked at $DIR/issue-65419-async-fn-resume-after-completion.rs:11:16:
+`async fn` resumed after completion
+note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

tests/ui/async-await/issues/issue-65419/issue-65419-async-fn-resume-after-panic.rs

@@ -3,8 +3,8 @@
 
 //@ run-fail
 //@ needs-unwind
-//@ error-pattern: thread 'main' panicked
-//@ error-pattern: `async fn` resumed after panicking
+//@ check-run-results: thread 'main' panicked
+//@ check-run-results: `async fn` resumed after panicking
 //@ edition:2018
 
 #![feature(coroutines, coroutine_trait)]