Explorar o código

test: regenerate tests broken by line number changes

Yes, we shouldn't have to do this.

Signed-off-by: Christina Sørensen <christina@cafkafk.com>
Christina Sørensen hai 1 ano
pai
achega
92fea94284

+ 1 - 1
tests/gen/long_time_style_custom_non_recent_empty_nix.stderr

@@ -1,2 +1,2 @@
-thread 'main' panicked at 'Custom timestamp format is empty, please supply a chrono format string after the plus sign.', src/options/view.rs:353:21
+thread 'main' panicked at 'Custom timestamp format is empty, please supply a chrono format string after the plus sign.', src/options/view.rs:357:21
 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

+ 1 - 1
tests/gen/long_time_style_custom_non_recent_none_nix.stderr

@@ -1,2 +1,2 @@
-thread 'main' panicked at 'Custom timestamp format is empty, please supply a chrono format string after the plus sign.', src/options/view.rs:351:47
+thread 'main' panicked at 'Custom timestamp format is empty, please supply a chrono format string after the plus sign.', src/options/view.rs:355:47
 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

+ 1 - 1
tests/gen/long_time_style_custom_recent_empty_nix.stderr

@@ -1,2 +1,2 @@
-thread 'main' panicked at 'Custom timestamp format for recent files is empty, please supply a chrono format string at the second line.', src/options/view.rs:367:25
+thread 'main' panicked at 'Custom timestamp format for recent files is empty, please supply a chrono format string at the second line.', src/options/view.rs:371:25
 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace