Update ui output to latest nightly

diff --git a/tests/ui/fallible_impl_from.stderr b/tests/ui/fallible_impl_from.stderr
index 448a1fe0559aa754abb5a3c2a797e6fbde764e41..8e93966ccd12d45778c0a258861a81e9ba06ef88 100644 (file)
--- a/tests/ui/fallible_impl_from.stderr
+++ b/tests/ui/fallible_impl_from.stderr
@@ -38,7 +38,7 @@ note: potential failure(s)
    |
 31 |             panic!();
    |             ^^^^^^^^^
-   = note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)
+   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
 
 error: consider implementing `TryFrom` instead
   --> $DIR/fallible_impl_from.rs:37:1
@@ -65,7 +65,7 @@ note: potential failure(s)
    |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
 43 |             panic!("{:?}", s);
    |             ^^^^^^^^^^^^^^^^^^
-   = note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)
+   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
 
 error: consider implementing `TryFrom` instead
   --> $DIR/fallible_impl_from.rs:55:1
@@ -87,5 +87,5 @@ note: potential failure(s)
    |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 58 |             panic!("{:?}", s);
    |             ^^^^^^^^^^^^^^^^^^
-   = note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)
+   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
 

diff --git a/tests/ui/matches.stderr b/tests/ui/matches.stderr
index 8ddb12b653c2c3e26d3cc0a8d1608292bc51f427..bcb94bab26c34db606aa4b24bfff183355d94f86 100644 (file)
--- a/tests/ui/matches.stderr
+++ b/tests/ui/matches.stderr
@@ -264,7 +264,7 @@ note: consider refactoring into `Ok(3) | Ok(_)`
     |
 238 |         Ok(3) => println!("ok"),
     |                  ^^^^^^^^^^^^^^
-    = note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)
+    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
 
 error: Err(_) will match all errors, maybe not a good idea
    --> $DIR/matches.rs:246:9
@@ -290,7 +290,7 @@ note: consider refactoring into `Ok(3) | Ok(_)`
     |
 244 |         Ok(3) => println!("ok"),
     |                  ^^^^^^^^^^^^^^
-    = note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)
+    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
 
 error: Err(_) will match all errors, maybe not a good idea
    --> $DIR/matches.rs:252:9
@@ -316,7 +316,7 @@ note: consider refactoring into `Ok(3) | Ok(_)`
     |
 250 |         Ok(3) => println!("ok"),
     |                  ^^^^^^^^^^^^^^
-    = note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)
+    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
 
 error: this `match` has identical arm bodies
    --> $DIR/matches.rs:258:18
@@ -334,7 +334,7 @@ note: consider refactoring into `Ok(3) | Ok(_)`
     |
 257 |         Ok(3) => println!("ok"),
     |                  ^^^^^^^^^^^^^^
-    = note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)
+    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
 
 error: this `match` has identical arm bodies
    --> $DIR/matches.rs:265:18
@@ -352,7 +352,7 @@ note: consider refactoring into `Ok(3) | Ok(_)`
     |
 264 |         Ok(3) => println!("ok"),
     |                  ^^^^^^^^^^^^^^
-    = note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)
+    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
 
 error: this `match` has identical arm bodies
    --> $DIR/matches.rs:271:18
@@ -370,7 +370,7 @@ note: consider refactoring into `Ok(3) | Ok(_)`
     |
 270 |         Ok(3) => println!("ok"),
     |                  ^^^^^^^^^^^^^^
-    = note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)
+    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
 
 error: this `match` has identical arm bodies
    --> $DIR/matches.rs:277:18
@@ -388,5 +388,5 @@ note: consider refactoring into `Ok(3) | Ok(_)`
     |
 276 |         Ok(3) => println!("ok"),
     |                  ^^^^^^^^^^^^^^
-    = note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)
+    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
 

diff --git a/tests/ui/regex.stderr b/tests/ui/regex.stderr
index 9f1397990bbfbacec30229ffe968496ef89efaab..1c244c1df127e57511d1d82794256726ce4e4301 100644 (file)
--- a/tests/ui/regex.stderr
+++ b/tests/ui/regex.stderr
@@ -112,7 +112,7 @@ error: trivial regex
 error: trivial regex
   --> $DIR/regex.rs:62:40
    |
-62 |     let trivial_backslash = Regex::new("a/.b");
+62 |     let trivial_backslash = Regex::new("a//.b");
    |                                        ^^^^^^^
    |
    = help: consider using consider using `str::contains`

diff --git a/tests/ui/unused_io_amount.stderr b/tests/ui/unused_io_amount.stderr
index 0ec8615a0105591e4758851679b08443b12d7e19..b4a3cb2122df70ca6fb9e1e926cd505f497df902 100644 (file)
--- a/tests/ui/unused_io_amount.stderr
+++ b/tests/ui/unused_io_amount.stderr
@@ -5,7 +5,7 @@ error: handle written amount returned or use `Write::write_all` instead
    |     ^^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: `-D unused-io-amount` implied by `-D warnings`
-   = note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)
+   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
 
 error: handle read amount returned or use `Read::read_exact` instead
   --> $DIR/unused_io_amount.rs:13:5
@@ -13,7 +13,7 @@ error: handle read amount returned or use `Read::read_exact` instead
 13 |     try!(s.read(&mut buf));
    |     ^^^^^^^^^^^^^^^^^^^^^^^
    |
-   = note: this error originates in a macro outside of the current crate (run with -Z external-macro-backtrace for more info)
+   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
 
 error: handle written amount returned or use `Write::write_all` instead
   --> $DIR/unused_io_amount.rs:18:5