[INFO] cloning repository https://github.com/swindon-rs/swindon [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/swindon-rs/swindon" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fswindon-rs%2Fswindon", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fswindon-rs%2Fswindon'... [INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }` [INFO] [stdout] a4b912d678b4159624b53870b1670134fbc32d91 [INFO] checking swindon-rs/swindon against try#ddfd70ee3c3748e597b32f416b0d15a4f6e37685 for pr-87050 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fswindon-rs%2Fswindon" "/workspace/builds/worker-5/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-5/source'... [INFO] [stderr] done. [INFO] validating manifest of git repo https://github.com/swindon-rs/swindon on toolchain ddfd70ee3c3748e597b32f416b0d15a4f6e37685 [INFO] running `Command { std: "/workspace/cargo-home/bin/cargo" "+ddfd70ee3c3748e597b32f416b0d15a4f6e37685" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] started tweaking git repo https://github.com/swindon-rs/swindon [INFO] finished tweaking git repo https://github.com/swindon-rs/swindon [INFO] tweaked toml for git repo https://github.com/swindon-rs/swindon written to /workspace/builds/worker-5/source/Cargo.toml [INFO] crate git repo https://github.com/swindon-rs/swindon already has a lockfile, it will not be regenerated [INFO] running `Command { std: "/workspace/cargo-home/bin/cargo" "+ddfd70ee3c3748e597b32f416b0d15a4f6e37685" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded proc-macro2 v1.0.4 [INFO] [stderr] Downloaded assert_matches v1.3.0 [INFO] [stderr] Downloaded httpbin v0.3.3 [INFO] [stderr] Downloaded quire v0.3.1 [INFO] [stderr] Downloaded tokio-threadpool v0.1.16 [INFO] [stderr] Downloaded string-intern v0.1.7 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:34b6a614d2c27851fe6cbf88fbd1137609cefab8b10d0615aaeb6fd47975d74e" "/opt/rustwide/cargo-home/bin/cargo" "+ddfd70ee3c3748e597b32f416b0d15a4f6e37685" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 2d49f0de4202031e91c58dcf2d4c66f00c29c9fd6a97db74b7658c4f3ec4cc17 [INFO] running `Command { std: "docker" "start" "-a" "2d49f0de4202031e91c58dcf2d4c66f00c29c9fd6a97db74b7658c4f3ec4cc17", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "2d49f0de4202031e91c58dcf2d4c66f00c29c9fd6a97db74b7658c4f3ec4cc17", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "2d49f0de4202031e91c58dcf2d4c66f00c29c9fd6a97db74b7658c4f3ec4cc17", kill_on_drop: false }` [INFO] [stdout] 2d49f0de4202031e91c58dcf2d4c66f00c29c9fd6a97db74b7658c4f3ec4cc17 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:34b6a614d2c27851fe6cbf88fbd1137609cefab8b10d0615aaeb6fd47975d74e" "/opt/rustwide/cargo-home/bin/cargo" "+ddfd70ee3c3748e597b32f416b0d15a4f6e37685" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] ce99f36c0a47f551d1eda5f93e0fb0f6b5154f2964c925cccbe732fdbfcec989 [INFO] running `Command { std: "docker" "start" "-a" "ce99f36c0a47f551d1eda5f93e0fb0f6b5154f2964c925cccbe732fdbfcec989", kill_on_drop: false }` [INFO] [stderr] Compiling libc v0.2.62 [INFO] [stderr] Compiling autocfg v0.1.6 [INFO] [stderr] Compiling serde v1.0.101 [INFO] [stderr] Compiling winapi-build v0.1.1 [INFO] [stderr] Compiling proc-macro2 v1.0.4 [INFO] [stderr] Checking scoped-tls v0.1.2 [INFO] [stderr] Checking winapi v0.2.8 [INFO] [stderr] Compiling syn v1.0.5 [INFO] [stderr] Checking httpdate v0.3.2 [INFO] [stderr] Checking netbuf v0.4.1 [INFO] [stderr] Checking regex-syntax v0.3.9 [INFO] [stderr] Checking constant_time_eq v0.1.4 [INFO] [stderr] Checking sha1 v0.4.0 [INFO] [stderr] Checking utf8-ranges v0.1.3 [INFO] [stderr] Checking byte-tools v0.2.0 [INFO] [stderr] Checking argparse v0.2.2 [INFO] [stderr] Checking ascii v0.7.1 [INFO] [stderr] Checking atomic v0.3.4 [INFO] [stderr] Checking quick-error v2.0.0 [INFO] [stderr] Checking crossbeam v0.3.2 [INFO] [stderr] Checking assert_matches v1.3.0 [INFO] [stderr] Checking crossbeam-utils v0.6.6 [INFO] [stderr] Checking tokio-sync v0.1.6 [INFO] [stderr] Compiling rand_core v0.3.1 [INFO] [stderr] Checking thread_local v0.3.6 [INFO] [stderr] Checking humantime v1.3.0 [INFO] [stderr] Checking async-slot v0.1.0 [INFO] [stderr] Checking regex-syntax v0.5.6 [INFO] [stderr] Checking owning_ref v0.3.3 [INFO] [stderr] Checking idna v0.1.5 [INFO] [stderr] Compiling parking_lot_core v0.6.2 [INFO] [stderr] Compiling parking_lot v0.9.0 [INFO] [stderr] Compiling memoffset v0.5.1 [INFO] [stderr] Checking aho-corasick v0.6.10 [INFO] [stderr] Checking generic-array v0.9.0 [INFO] [stderr] Checking generic-array v0.11.1 [INFO] [stderr] Compiling phf_shared v0.7.24 [INFO] [stderr] Compiling rand_hc v0.1.0 [INFO] [stderr] Compiling rand_isaac v0.1.1 [INFO] [stderr] Compiling rand_xorshift v0.1.1 [INFO] [stderr] Checking regex v1.3.1 [INFO] [stderr] Checking tokio-executor v0.1.8 [INFO] [stderr] Checking crossbeam-queue v0.1.2 [INFO] [stderr] Checking combine v2.5.2 [INFO] [stderr] Compiling kernel32-sys v0.2.2 [INFO] [stderr] Checking phf v0.7.24 [INFO] [stderr] Checking url v1.7.2 [INFO] [stderr] Checking digest v0.7.6 [INFO] [stderr] Checking crypto-mac v0.5.2 [INFO] [stderr] Compiling rand_chacha v0.1.1 [INFO] [stderr] Compiling rand_pcg v0.1.2 [INFO] [stderr] Compiling rand v0.6.5 [INFO] [stderr] Compiling num-traits v0.2.8 [INFO] [stderr] Checking tokio-timer v0.2.11 [INFO] [stderr] Checking tokio-current-thread v0.1.6 [INFO] [stderr] Checking digest-writer v0.3.1 [INFO] [stderr] Checking blake2 v0.7.1 [INFO] [stderr] Checking crossbeam-epoch v0.7.2 [INFO] [stderr] Checking crossbeam-deque v0.7.1 [INFO] [stderr] Compiling rand_os v0.1.3 [INFO] [stderr] Compiling quote v1.0.2 [INFO] [stderr] Checking iovec v0.1.2 [INFO] [stderr] Checking num_cpus v1.10.1 [INFO] [stderr] Checking net2 v0.2.33 [INFO] [stderr] Checking rand v0.4.6 [INFO] [stderr] Checking memchr v0.1.11 [INFO] [stderr] Checking thread-id v2.0.0 [INFO] [stderr] Checking atty v0.2.13 [INFO] [stderr] Checking time v0.1.42 [INFO] [stderr] Checking thread_local v0.2.7 [INFO] [stderr] Checking bytes v0.4.12 [INFO] [stderr] Checking env_logger v0.5.13 [INFO] [stderr] Checking aho-corasick v0.5.3 [INFO] [stderr] Checking tokio-threadpool v0.1.16 [INFO] [stderr] Checking futures-cpupool v0.1.8 [INFO] [stderr] Checking num-traits v0.1.43 [INFO] [stderr] Checking mio v0.6.19 [INFO] [stderr] Checking humannum v0.1.0 [INFO] [stderr] Checking tokio-io v0.1.12 [INFO] [stderr] Checking regex v0.1.80 [INFO] [stderr] Compiling phf_generator v0.7.24 [INFO] [stderr] Compiling phf_codegen v0.7.24 [INFO] [stderr] Compiling mime_guess v1.8.7 [INFO] [stderr] Checking tokio-codec v0.1.1 [INFO] [stderr] Checking tk-bufstream v0.3.0 [INFO] [stderr] Checking env_logger v0.3.5 [INFO] [stderr] Checking tokio-fs v0.1.6 [INFO] [stderr] Checking abstract-ns v0.4.3 [INFO] [stderr] Checking regex v0.2.11 [INFO] [stderr] Checking ns-std-threaded v0.3.0 [INFO] [stderr] Checking tokio-reactor v0.1.10 [INFO] [stderr] Checking mio-uds v0.6.7 [INFO] [stderr] Checking tokio-tcp v0.1.3 [INFO] [stderr] Checking tokio-udp v0.1.5 [INFO] [stderr] Checking tokio-uds v0.2.5 [INFO] [stderr] Checking serde_json v1.0.40 [INFO] [stderr] Checking string-intern v0.1.7 [INFO] [stderr] Checking tokio v0.1.22 [INFO] [stderr] Checking quire v0.3.1 [INFO] [stderr] Checking tokio-core v0.1.17 [INFO] [stderr] Compiling serde_derive v1.0.101 [INFO] [stderr] Checking http-file-headers v0.1.8 [INFO] [stderr] Checking trimmer v0.3.6 [INFO] [stderr] Checking libcantal v0.3.2 [INFO] [stderr] Checking tk-http v0.3.9 [INFO] [stderr] Checking tk-listen v0.1.1 [INFO] [stderr] Checking tk-pool v0.5.3 [INFO] [stderr] Checking ns-router v0.1.6 [INFO] [stderr] Checking httpbin v0.3.3 [INFO] [stderr] Checking self-meter v0.6.0 [INFO] [stderr] Checking self-meter-http v0.4.1 [INFO] [stderr] Checking swindon v0.7.8 (/opt/rustwide/workdir) [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:162:25 [INFO] [stdout] | [INFO] [stdout] 162 | format!("unexpectedly valid: {}", $a)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 173 | / error_starts!( [INFO] [stdout] 174 | | "", [INFO] [stdout] 175 | | "EOF while parsing a value" [INFO] [stdout] 176 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(non_fmt_panics)]` on by default [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 162 | "unexpectedly valid: {}", $a); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:165:25 [INFO] [stdout] | [INFO] [stdout] 165 | format!("{}: {} != {}", $a, err, $b)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 173 | / error_starts!( [INFO] [stdout] 174 | | "", [INFO] [stdout] 175 | | "EOF while parsing a value" [INFO] [stdout] 176 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 165 | "{}: {} != {}", $a, err, $b); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:162:25 [INFO] [stdout] | [INFO] [stdout] 162 | format!("unexpectedly valid: {}", $a)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 177 | / error_starts!( [INFO] [stdout] 178 | | "[invalid json", [INFO] [stdout] 179 | | "expected value at line 1" [INFO] [stdout] 180 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 162 | "unexpectedly valid: {}", $a); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:165:25 [INFO] [stdout] | [INFO] [stdout] 165 | format!("{}: {} != {}", $a, err, $b)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 177 | / error_starts!( [INFO] [stdout] 178 | | "[invalid json", [INFO] [stdout] 179 | | "expected value at line 1" [INFO] [stdout] 180 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 165 | "{}: {} != {}", $a, err, $b); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:162:25 [INFO] [stdout] | [INFO] [stdout] 162 | format!("unexpectedly valid: {}", $a)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 181 | / error_starts!( [INFO] [stdout] 182 | | "{}", [INFO] [stdout] 183 | | "invalid type: map, expected tuple struct" [INFO] [stdout] 184 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 162 | "unexpectedly valid: {}", $a); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:165:25 [INFO] [stdout] | [INFO] [stdout] 165 | format!("{}: {} != {}", $a, err, $b)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 181 | / error_starts!( [INFO] [stdout] 182 | | "{}", [INFO] [stdout] 183 | | "invalid type: map, expected tuple struct" [INFO] [stdout] 184 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 165 | "{}: {} != {}", $a, err, $b); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:162:25 [INFO] [stdout] | [INFO] [stdout] 162 | format!("unexpectedly valid: {}", $a)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 185 | / error_starts!( [INFO] [stdout] 186 | | "[]", [INFO] [stdout] 187 | | "invalid length 0" [INFO] [stdout] 188 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 162 | "unexpectedly valid: {}", $a); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:165:25 [INFO] [stdout] | [INFO] [stdout] 165 | format!("{}: {} != {}", $a, err, $b)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 185 | / error_starts!( [INFO] [stdout] 186 | | "[]", [INFO] [stdout] 187 | | "invalid length 0" [INFO] [stdout] 188 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 165 | "{}: {} != {}", $a, err, $b); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:162:25 [INFO] [stdout] | [INFO] [stdout] 162 | format!("unexpectedly valid: {}", $a)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 189 | / error_starts!( [INFO] [stdout] 190 | | "[1, 2, 3, 4, 5]", [INFO] [stdout] 191 | | "invalid type: integer `1`, expected a string" [INFO] [stdout] 192 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 162 | "unexpectedly valid: {}", $a); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:165:25 [INFO] [stdout] | [INFO] [stdout] 165 | format!("{}: {} != {}", $a, err, $b)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 189 | / error_starts!( [INFO] [stdout] 190 | | "[1, 2, 3, 4, 5]", [INFO] [stdout] 191 | | "invalid type: integer `1`, expected a string" [INFO] [stdout] 192 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 165 | "{}: {} != {}", $a, err, $b); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:162:25 [INFO] [stdout] | [INFO] [stdout] 162 | format!("unexpectedly valid: {}", $a)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 193 | / error_starts!( [INFO] [stdout] 194 | | "[1, 2, 3, 4]", [INFO] [stdout] 195 | | "invalid type: integer `1`, expected a string" [INFO] [stdout] 196 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 162 | "unexpectedly valid: {}", $a); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:165:25 [INFO] [stdout] | [INFO] [stdout] 165 | format!("{}: {} != {}", $a, err, $b)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 193 | / error_starts!( [INFO] [stdout] 194 | | "[1, 2, 3, 4]", [INFO] [stdout] 195 | | "invalid type: integer `1`, expected a string" [INFO] [stdout] 196 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 165 | "{}: {} != {}", $a, err, $b); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:162:25 [INFO] [stdout] | [INFO] [stdout] 162 | format!("unexpectedly valid: {}", $a)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 197 | / error_starts!( [INFO] [stdout] 198 | | "[null, null, null, 4]", [INFO] [stdout] 199 | | "invalid type: null, expected a string" [INFO] [stdout] 200 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 162 | "unexpectedly valid: {}", $a); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:165:25 [INFO] [stdout] | [INFO] [stdout] 165 | format!("{}: {} != {}", $a, err, $b)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 197 | / error_starts!( [INFO] [stdout] 198 | | "[null, null, null, 4]", [INFO] [stdout] 199 | | "invalid type: null, expected a string" [INFO] [stdout] 200 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 165 | "{}: {} != {}", $a, err, $b); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:162:25 [INFO] [stdout] | [INFO] [stdout] 162 | format!("unexpectedly valid: {}", $a)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 201 | / error_starts!( [INFO] [stdout] 202 | | "[\"1\", 2, 3, 4]", [INFO] [stdout] 203 | | "invalid type: integer `2`, expected a map" [INFO] [stdout] 204 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 162 | "unexpectedly valid: {}", $a); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:165:25 [INFO] [stdout] | [INFO] [stdout] 165 | format!("{}: {} != {}", $a, err, $b)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 201 | / error_starts!( [INFO] [stdout] 202 | | "[\"1\", 2, 3, 4]", [INFO] [stdout] 203 | | "invalid type: integer `2`, expected a map" [INFO] [stdout] 204 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 165 | "{}: {} != {}", $a, err, $b); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:162:25 [INFO] [stdout] | [INFO] [stdout] 162 | format!("unexpectedly valid: {}", $a)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 205 | / error_starts!( [INFO] [stdout] 206 | | "[\"1\", {}, 3, 4]", [INFO] [stdout] 207 | | "invalid type: integer `3`, expected a sequence" [INFO] [stdout] 208 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 162 | "unexpectedly valid: {}", $a); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:165:25 [INFO] [stdout] | [INFO] [stdout] 165 | format!("{}: {} != {}", $a, err, $b)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 205 | / error_starts!( [INFO] [stdout] 206 | | "[\"1\", {}, 3, 4]", [INFO] [stdout] 207 | | "invalid type: integer `3`, expected a sequence" [INFO] [stdout] 208 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 165 | "{}: {} != {}", $a, err, $b); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:162:25 [INFO] [stdout] | [INFO] [stdout] 162 | format!("unexpectedly valid: {}", $a)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 209 | / error_starts!( [INFO] [stdout] 210 | | "[\"1\", {}, [], 4]", [INFO] [stdout] 211 | | "invalid type: integer `4`, expected a map" [INFO] [stdout] 212 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 162 | "unexpectedly valid: {}", $a); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:165:25 [INFO] [stdout] | [INFO] [stdout] 165 | format!("{}: {} != {}", $a, err, $b)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 209 | / error_starts!( [INFO] [stdout] 210 | | "[\"1\", {}, [], 4]", [INFO] [stdout] 211 | | "invalid type: integer `4`, expected a map" [INFO] [stdout] 212 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 165 | "{}: {} != {}", $a, err, $b); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 20 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:162:25 [INFO] [stdout] | [INFO] [stdout] 162 | format!("unexpectedly valid: {}", $a)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 173 | / error_starts!( [INFO] [stdout] 174 | | "", [INFO] [stdout] 175 | | "EOF while parsing a value" [INFO] [stdout] 176 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(non_fmt_panics)]` on by default [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 162 | "unexpectedly valid: {}", $a); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:165:25 [INFO] [stdout] | [INFO] [stdout] 165 | format!("{}: {} != {}", $a, err, $b)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 173 | / error_starts!( [INFO] [stdout] 174 | | "", [INFO] [stdout] 175 | | "EOF while parsing a value" [INFO] [stdout] 176 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 165 | "{}: {} != {}", $a, err, $b); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:162:25 [INFO] [stdout] | [INFO] [stdout] 162 | format!("unexpectedly valid: {}", $a)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 177 | / error_starts!( [INFO] [stdout] 178 | | "[invalid json", [INFO] [stdout] 179 | | "expected value at line 1" [INFO] [stdout] 180 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 162 | "unexpectedly valid: {}", $a); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:165:25 [INFO] [stdout] | [INFO] [stdout] 165 | format!("{}: {} != {}", $a, err, $b)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 177 | / error_starts!( [INFO] [stdout] 178 | | "[invalid json", [INFO] [stdout] 179 | | "expected value at line 1" [INFO] [stdout] 180 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 165 | "{}: {} != {}", $a, err, $b); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:162:25 [INFO] [stdout] | [INFO] [stdout] 162 | format!("unexpectedly valid: {}", $a)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 181 | / error_starts!( [INFO] [stdout] 182 | | "{}", [INFO] [stdout] 183 | | "invalid type: map, expected tuple struct" [INFO] [stdout] 184 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 162 | "unexpectedly valid: {}", $a); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:165:25 [INFO] [stdout] | [INFO] [stdout] 165 | format!("{}: {} != {}", $a, err, $b)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 181 | / error_starts!( [INFO] [stdout] 182 | | "{}", [INFO] [stdout] 183 | | "invalid type: map, expected tuple struct" [INFO] [stdout] 184 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 165 | "{}: {} != {}", $a, err, $b); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:162:25 [INFO] [stdout] | [INFO] [stdout] 162 | format!("unexpectedly valid: {}", $a)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 185 | / error_starts!( [INFO] [stdout] 186 | | "[]", [INFO] [stdout] 187 | | "invalid length 0" [INFO] [stdout] 188 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 162 | "unexpectedly valid: {}", $a); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:165:25 [INFO] [stdout] | [INFO] [stdout] 165 | format!("{}: {} != {}", $a, err, $b)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 185 | / error_starts!( [INFO] [stdout] 186 | | "[]", [INFO] [stdout] 187 | | "invalid length 0" [INFO] [stdout] 188 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 165 | "{}: {} != {}", $a, err, $b); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:162:25 [INFO] [stdout] | [INFO] [stdout] 162 | format!("unexpectedly valid: {}", $a)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 189 | / error_starts!( [INFO] [stdout] 190 | | "[1, 2, 3, 4, 5]", [INFO] [stdout] 191 | | "invalid type: integer `1`, expected a string" [INFO] [stdout] 192 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 162 | "unexpectedly valid: {}", $a); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:165:25 [INFO] [stdout] | [INFO] [stdout] 165 | format!("{}: {} != {}", $a, err, $b)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 189 | / error_starts!( [INFO] [stdout] 190 | | "[1, 2, 3, 4, 5]", [INFO] [stdout] 191 | | "invalid type: integer `1`, expected a string" [INFO] [stdout] 192 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 165 | "{}: {} != {}", $a, err, $b); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:162:25 [INFO] [stdout] | [INFO] [stdout] 162 | format!("unexpectedly valid: {}", $a)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 193 | / error_starts!( [INFO] [stdout] 194 | | "[1, 2, 3, 4]", [INFO] [stdout] 195 | | "invalid type: integer `1`, expected a string" [INFO] [stdout] 196 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 162 | "unexpectedly valid: {}", $a); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:165:25 [INFO] [stdout] | [INFO] [stdout] 165 | format!("{}: {} != {}", $a, err, $b)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 193 | / error_starts!( [INFO] [stdout] 194 | | "[1, 2, 3, 4]", [INFO] [stdout] 195 | | "invalid type: integer `1`, expected a string" [INFO] [stdout] 196 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 165 | "{}: {} != {}", $a, err, $b); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:162:25 [INFO] [stdout] | [INFO] [stdout] 162 | format!("unexpectedly valid: {}", $a)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 197 | / error_starts!( [INFO] [stdout] 198 | | "[null, null, null, 4]", [INFO] [stdout] 199 | | "invalid type: null, expected a string" [INFO] [stdout] 200 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 162 | "unexpectedly valid: {}", $a); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:165:25 [INFO] [stdout] | [INFO] [stdout] 165 | format!("{}: {} != {}", $a, err, $b)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 197 | / error_starts!( [INFO] [stdout] 198 | | "[null, null, null, 4]", [INFO] [stdout] 199 | | "invalid type: null, expected a string" [INFO] [stdout] 200 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 165 | "{}: {} != {}", $a, err, $b); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:162:25 [INFO] [stdout] | [INFO] [stdout] 162 | format!("unexpectedly valid: {}", $a)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 201 | / error_starts!( [INFO] [stdout] 202 | | "[\"1\", 2, 3, 4]", [INFO] [stdout] 203 | | "invalid type: integer `2`, expected a map" [INFO] [stdout] 204 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 162 | "unexpectedly valid: {}", $a); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:165:25 [INFO] [stdout] | [INFO] [stdout] 165 | format!("{}: {} != {}", $a, err, $b)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 201 | / error_starts!( [INFO] [stdout] 202 | | "[\"1\", 2, 3, 4]", [INFO] [stdout] 203 | | "invalid type: integer `2`, expected a map" [INFO] [stdout] 204 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 165 | "{}: {} != {}", $a, err, $b); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:162:25 [INFO] [stdout] | [INFO] [stdout] 162 | format!("unexpectedly valid: {}", $a)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 205 | / error_starts!( [INFO] [stdout] 206 | | "[\"1\", {}, 3, 4]", [INFO] [stdout] 207 | | "invalid type: integer `3`, expected a sequence" [INFO] [stdout] 208 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 162 | "unexpectedly valid: {}", $a); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:165:25 [INFO] [stdout] | [INFO] [stdout] 165 | format!("{}: {} != {}", $a, err, $b)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 205 | / error_starts!( [INFO] [stdout] 206 | | "[\"1\", {}, 3, 4]", [INFO] [stdout] 207 | | "invalid type: integer `3`, expected a sequence" [INFO] [stdout] 208 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 165 | "{}: {} != {}", $a, err, $b); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:162:25 [INFO] [stdout] | [INFO] [stdout] 162 | format!("unexpectedly valid: {}", $a)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 209 | / error_starts!( [INFO] [stdout] 210 | | "[\"1\", {}, [], 4]", [INFO] [stdout] 211 | | "invalid type: integer `4`, expected a map" [INFO] [stdout] 212 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 162 | "unexpectedly valid: {}", $a); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/chat/message.rs:165:25 [INFO] [stdout] | [INFO] [stdout] 165 | format!("{}: {} != {}", $a, err, $b)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 209 | / error_starts!( [INFO] [stdout] 210 | | "[\"1\", {}, [], 4]", [INFO] [stdout] 211 | | "invalid type: integer `4`, expected a map" [INFO] [stdout] 212 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: the assert!() macro supports formatting, so there's no need for the format!() macro here [INFO] [stdout] = note: this warning originates in the macro `error_starts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: remove the `format!(..)` macro call [INFO] [stdout] | [INFO] [stdout] 165 | "{}: {} != {}", $a, err, $b); [INFO] [stdout] | -- -- [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 20 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 37.37s [INFO] running `Command { std: "docker" "inspect" "ce99f36c0a47f551d1eda5f93e0fb0f6b5154f2964c925cccbe732fdbfcec989", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "ce99f36c0a47f551d1eda5f93e0fb0f6b5154f2964c925cccbe732fdbfcec989", kill_on_drop: false }` [INFO] [stdout] ce99f36c0a47f551d1eda5f93e0fb0f6b5154f2964c925cccbe732fdbfcec989