[INFO] fetching crate lightning-rapid-gossip-sync 0.0.125...
[INFO] checking lightning-rapid-gossip-sync-0.0.125 against try#31561a63598a0f21fc74c024747ef1310fdd2eb2 for pr-133536
[INFO] extracting crate lightning-rapid-gossip-sync 0.0.125 into /workspace/builds/worker-5-tc2/source
[INFO] validating manifest of crates.io crate lightning-rapid-gossip-sync 0.0.125 on toolchain 31561a63598a0f21fc74c024747ef1310fdd2eb2
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+31561a63598a0f21fc74c024747ef1310fdd2eb2" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] started tweaking crates.io crate lightning-rapid-gossip-sync 0.0.125
[INFO] finished tweaking crates.io crate lightning-rapid-gossip-sync 0.0.125
[INFO] tweaked toml for crates.io crate lightning-rapid-gossip-sync 0.0.125 written to /workspace/builds/worker-5-tc2/source/Cargo.toml
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+31561a63598a0f21fc74c024747ef1310fdd2eb2" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 76 packages to latest compatible versions
[INFO] [stderr]       Adding criterion v0.4.0 (available: v0.5.1)
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+31561a63598a0f21fc74c024747ef1310fdd2eb2" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc2/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:4a844ea9eb2546a2d2c7022eacef16ef2e8229c7fbb2c7d4d55a9ceca922f72d" "/opt/rustwide/cargo-home/bin/cargo" "+31561a63598a0f21fc74c024747ef1310fdd2eb2" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 977c75039e240f54455c8995f761da52cf7dd6cd20dfbae6b28399c1fba5672b
[INFO] running `Command { std: "docker" "start" "-a" "977c75039e240f54455c8995f761da52cf7dd6cd20dfbae6b28399c1fba5672b", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "977c75039e240f54455c8995f761da52cf7dd6cd20dfbae6b28399c1fba5672b", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "977c75039e240f54455c8995f761da52cf7dd6cd20dfbae6b28399c1fba5672b", kill_on_drop: false }`
[INFO] [stdout] 977c75039e240f54455c8995f761da52cf7dd6cd20dfbae6b28399c1fba5672b
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc2/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" "RUSTDOCFLAGS=--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:4a844ea9eb2546a2d2c7022eacef16ef2e8229c7fbb2c7d4d55a9ceca922f72d" "/opt/rustwide/cargo-home/bin/cargo" "+31561a63598a0f21fc74c024747ef1310fdd2eb2" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] bbb4a0fd6e88783b0781bc50ab3f361b879d79037f926a0f2cfda71757cdf4ee
[INFO] running `Command { std: "docker" "start" "-a" "bbb4a0fd6e88783b0781bc50ab3f361b879d79037f926a0f2cfda71757cdf4ee", kill_on_drop: false }`
[INFO] [stderr]    Compiling shlex v1.3.0
[INFO] [stderr]    Compiling bitcoin-io v0.1.3
[INFO] [stderr]     Checking arrayvec v0.7.6
[INFO] [stderr]    Compiling bitcoin-internals v0.3.0
[INFO] [stderr]    Compiling hex_lit v0.1.1
[INFO] [stderr]    Compiling bitcoin v0.32.5
[INFO] [stderr]     Checking memchr v2.7.4
[INFO] [stderr]     Checking bech32 v0.11.0
[INFO] [stderr]     Checking bech32 v0.9.1
[INFO] [stderr]     Checking regex-syntax v0.8.5
[INFO] [stderr]    Compiling cc v1.2.2
[INFO] [stderr]     Checking hex-conservative v0.2.1
[INFO] [stderr]     Checking bitcoin-units v0.1.2
[INFO] [stderr]     Checking bitcoin_hashes v0.14.0
[INFO] [stderr]     Checking aho-corasick v1.1.3
[INFO] [stderr]    Compiling secp256k1-sys v0.10.1
[INFO] [stderr]    Compiling bitcoinconsensus v0.105.0+25.1
[INFO] [stderr]     Checking base58ck v0.1.0
[INFO] [stderr]     Checking regex-automata v0.4.9
[INFO] [stderr]     Checking regex v1.11.1
[INFO] [stderr]     Checking secp256k1 v0.29.1
[INFO] [stderr]     Checking lightning-types v0.1.0
[INFO] [stderr]     Checking lightning-invoice v0.32.0
[INFO] [stderr]     Checking lightning v0.0.125
[INFO] [stderr]     Checking lightning-rapid-gossip-sync v0.0.125 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unexpected `cfg` condition name: `ldk_bench`
[INFO] [stdout]   --> src/lib.rs:65:7
[INFO] [stdout]    |
[INFO] [stdout] 65 | #[cfg(ldk_bench)]
[INFO] [stdout]    |       ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `fmt_debug`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows`
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(ldk_bench)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(ldk_bench)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `ldk_bench`
[INFO] [stdout]    --> src/lib.rs:319:7
[INFO] [stdout]     |
[INFO] [stdout] 319 | #[cfg(ldk_bench)]
[INFO] [stdout]     |       ^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(ldk_bench)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(ldk_bench)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `ldk_bench`
[INFO] [stdout]   --> src/lib.rs:65:7
[INFO] [stdout]    |
[INFO] [stdout] 65 | #[cfg(ldk_bench)]
[INFO] [stdout]    |       ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `fmt_debug`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows`
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(ldk_bench)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(ldk_bench)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `ldk_bench`
[INFO] [stdout]    --> src/lib.rs:319:7
[INFO] [stdout]     |
[INFO] [stdout] 319 | #[cfg(ldk_bench)]
[INFO] [stdout]     |       ^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(ldk_bench)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(ldk_bench)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]   --> src/processing.rs:68:3
[INFO] [stdout]    |
[INFO] [stdout] 68 |         log_trace!(self.logger, "Processing RGS data...");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]    = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:198:9
[INFO] [stdout]     |
[INFO] [stdout] 198 | / ...                   log_gossip!(
[INFO] [stdout] 199 | | ...                       self.logger,
[INFO] [stdout] 200 | | ...                       "Failure to parse address at index {} for node ID {}",
[INFO] [stdout] 201 | | ...                       address_index,
[INFO] [stdout] 202 | | ...                       current_node_id
[INFO] [stdout] 203 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:228:6
[INFO] [stdout]     |
[INFO] [stdout] 228 | /                     log_gossip!(
[INFO] [stdout] 229 | |                         self.logger,
[INFO] [stdout] 230 | |                         "Ignoring {} bytes of additional data in node announcement",
[INFO] [stdout] 231 | |                         additional_data.len()
[INFO] [stdout] 232 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:265:4
[INFO] [stdout]     |
[INFO] [stdout] 265 | /             log_gossip!(
[INFO] [stdout] 266 | |                 self.logger,
[INFO] [stdout] 267 | |                 "Adding channel {} from RGS announcement at {}",
[INFO] [stdout] 268 | |                 short_channel_id,
[INFO] [stdout] 269 | |                 latest_seen_timestamp
[INFO] [stdout] 270 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:283:6
[INFO] [stdout]     |
[INFO] [stdout] 283 | /                     log_warn!(
[INFO] [stdout] 284 | |                         self.logger,
[INFO] [stdout] 285 | |                         "Failed to process channel announcement: {:?}",
[INFO] [stdout] 286 | |                         lightning_error
[INFO] [stdout] 287 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_warn` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:295:5
[INFO] [stdout]     |
[INFO] [stdout] 295 | /                 log_gossip!(
[INFO] [stdout] 296 | |                     self.logger,
[INFO] [stdout] 297 | |                     "Ignoring {} bytes of additional data in channel announcement",
[INFO] [stdout] 298 | |                     additional_data.len()
[INFO] [stdout] 299 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:436:4
[INFO] [stdout]     |
[INFO] [stdout] 436 | /             log_gossip!(
[INFO] [stdout] 437 | |                 self.logger,
[INFO] [stdout] 438 | |                 "Updating channel {} with flags {} from RGS announcement at {}",
[INFO] [stdout] 439 | |                 short_channel_id,
[INFO] [stdout] 440 | |                 channel_flags,
[INFO] [stdout] 441 | |                 latest_seen_timestamp
[INFO] [stdout] 442 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:308:6
[INFO] [stdout]     |
[INFO] [stdout] 308 | /                     log_given_level!(
[INFO] [stdout] 309 | |                         self.logger,
[INFO] [stdout] 310 | |                         level,
[INFO] [stdout] 311 | |                         "Failed to apply node announcement: {:?}",
[INFO] [stdout] 312 | |                         err
[INFO] [stdout] 313 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:447:6
[INFO] [stdout]     |
[INFO] [stdout] 447 | /                     log_given_level!(
[INFO] [stdout] 448 | |                         self.logger,
[INFO] [stdout] 449 | |                         level,
[INFO] [stdout] 450 | |                         "Failed to apply channel update: {:?}",
[INFO] [stdout] 451 | |                         err
[INFO] [stdout] 452 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log_given_level` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:316:6
[INFO] [stdout]     |
[INFO] [stdout] 316 |                     log_gossip!(self.logger, "Failed to apply node announcement: {:?}", err);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:466:3
[INFO] [stdout]     |
[INFO] [stdout] 466 |         log_trace!(self.logger, "Done processing RGS data from {}", latest_seen_timestamp);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:326:3
[INFO] [stdout]     |
[INFO] [stdout] 326 | /         log_debug!(self.logger, "Processing RGS update from {} with {} nodes, {} channel announcements and {} channel updates.",
[INFO] [stdout] 327 | |             latest_seen_timestamp, node_id_count, announcement_count, update_count);
[INFO] [stdout]     | |___________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_warn` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_info` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_debug` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/processing.rs:357:6
[INFO] [stdout]     |
[INFO] [stdout] 357 | /                     log_gossip!(
[INFO] [stdout] 358 | |                         self.logger,
[INFO] [stdout] 359 | |                         "Ignoring {} bytes of additional data in channel update",
[INFO] [stdout] 360 | |                         additional_data.len()
[INFO] [stdout] 361 | |                     );
[INFO] [stdout]     | |_____________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_trace` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_gossip` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_off` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/processing.rs:400:6
[INFO] [stdout]     |
[INFO] [stdout] 400 | /                     log_trace!(self.logger,
[INFO] [stdout] 401 | |                         "Skipping application of channel update for chan {} with flags {} as original data is missing.",
[INFO] [stdout] 402 | |                         short_channel_id, channel_flags);
[INFO] [stdout]     | |________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `criterion`, `default`, and `std`
[INFO] [stdout]     = help: consider adding `max_level_error` as a feature in `Cargo.toml`
[WARN] too many lines in the log, truncating it
