[INFO] fetching crate lightning-liquidity 0.1.0-alpha.6...
[INFO] checking lightning-liquidity-0.1.0-alpha.6 against try#31561a63598a0f21fc74c024747ef1310fdd2eb2 for pr-133536
[INFO] extracting crate lightning-liquidity 0.1.0-alpha.6 into /workspace/builds/worker-6-tc2/source
[INFO] validating manifest of crates.io crate lightning-liquidity 0.1.0-alpha.6 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-liquidity 0.1.0-alpha.6
[INFO] removed 0 missing tests
[INFO] finished tweaking crates.io crate lightning-liquidity 0.1.0-alpha.6
[INFO] tweaked toml for crates.io crate lightning-liquidity 0.1.0-alpha.6 written to /workspace/builds/worker-6-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 102 packages to latest compatible versions
[INFO] [stderr]       Adding hashbrown v0.8.2 (available: v0.15.2)
[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-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-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] e97403fad5b2274d6ccc7b84e6d99a24f177a77964527dea9bc1c2d894fcb073
[INFO] running `Command { std: "docker" "start" "-a" "e97403fad5b2274d6ccc7b84e6d99a24f177a77964527dea9bc1c2d894fcb073", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "e97403fad5b2274d6ccc7b84e6d99a24f177a77964527dea9bc1c2d894fcb073", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "e97403fad5b2274d6ccc7b84e6d99a24f177a77964527dea9bc1c2d894fcb073", kill_on_drop: false }`
[INFO] [stdout] e97403fad5b2274d6ccc7b84e6d99a24f177a77964527dea9bc1c2d894fcb073
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-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] 00a34cab348b90c3c10f5f97f7e9783b78d1f677ebde9b94e8feab41b974b8bd
[INFO] running `Command { std: "docker" "start" "-a" "00a34cab348b90c3c10f5f97f7e9783b78d1f677ebde9b94e8feab41b974b8bd", kill_on_drop: false }`
[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 secp256k1-sys v0.10.1
[INFO] [stderr]    Compiling bitcoinconsensus v0.105.0+25.1
[INFO] [stderr]    Compiling bitcoin v0.32.5
[INFO] [stderr]    Compiling syn v2.0.90
[INFO] [stderr]     Checking hex-conservative v0.2.1
[INFO] [stderr]     Checking memchr v2.7.4
[INFO] [stderr]     Checking bech32 v0.11.0
[INFO] [stderr]     Checking bech32 v0.9.1
[INFO] [stderr]    Compiling num-traits v0.2.19
[INFO] [stderr]     Checking byteorder v1.5.0
[INFO] [stderr]    Compiling rustix v0.38.41
[INFO] [stderr]     Checking bitflags v2.6.0
[INFO] [stderr]     Checking linux-raw-sys v0.4.14
[INFO] [stderr]     Checking once_cell v1.20.2
[INFO] [stderr]     Checking fastrand v2.2.0
[INFO] [stderr]     Checking wait-timeout v0.2.0
[INFO] [stderr]     Checking aho-corasick v1.1.3
[INFO] [stderr]     Checking quick-error v1.2.3
[INFO] [stderr]     Checking bit-vec v0.6.3
[INFO] [stderr]     Checking rand_xorshift v0.3.0
[INFO] [stderr]     Checking unarray v0.1.4
[INFO] [stderr]     Checking bit-set v0.5.3
[INFO] [stderr]     Checking regex-automata v0.4.9
[INFO] [stderr]     Checking tempfile v3.14.0
[INFO] [stderr]     Checking rusty-fork v0.3.0
[INFO] [stderr]    Compiling serde_derive v1.0.215
[INFO] [stderr]    Compiling zerocopy-derive v0.7.35
[INFO] [stderr]    Compiling tokio-macros v2.4.0
[INFO] [stderr]     Checking regex v1.11.1
[INFO] [stderr]     Checking zerocopy v0.7.35
[INFO] [stderr]     Checking tokio v1.41.1
[INFO] [stderr]     Checking ppv-lite86 v0.2.20
[INFO] [stderr]     Checking rand_chacha v0.3.1
[INFO] [stderr]     Checking rand v0.8.5
[INFO] [stderr]     Checking proptest v1.5.0
[INFO] [stderr]     Checking serde v1.0.215
[INFO] [stderr]     Checking bitcoin_hashes v0.14.0
[INFO] [stderr]     Checking chrono v0.4.38
[INFO] [stderr]     Checking serde_json v1.0.133
[INFO] [stderr]     Checking bitcoin-units v0.1.2
[INFO] [stderr]     Checking secp256k1 v0.29.1
[INFO] [stderr]     Checking base58ck v0.1.0
[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
[INFO] [stderr]     Checking lightning-persister v0.0.125
[INFO] [stderr]     Checking lightning-liquidity v0.1.0-alpha.6 (/opt/rustwide/workdir)
[INFO] [stderr]     Checking lightning-background-processor v0.0.125
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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: requested on the command line with `-F unexpected-cfgs`
[INFO] [stdout]    = note: this error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:41:4
[INFO] [stdout]    |
[INFO] [stdout] 41 |             log_error!(node.logger, "Failed to register inbound payment: {:?}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:55:3
[INFO] [stdout]    |
[INFO] [stdout] 55 |         log_error!(node.logger, "Invalid payment hash: {:?}", e);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]   --> tests/lsps2_integration_tests.rs:78:4
[INFO] [stdout]    |
[INFO] [stdout] 78 |             log_error!(node.logger, "Failed to build and sign invoice: {}", e);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `hashbrown`, `no-std`, 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 error originates in the macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `lightning-liquidity` (test "lsps2_integration_tests") due to 81 previous errors
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] running `Command { std: "docker" "inspect" "00a34cab348b90c3c10f5f97f7e9783b78d1f677ebde9b94e8feab41b974b8bd", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "00a34cab348b90c3c10f5f97f7e9783b78d1f677ebde9b94e8feab41b974b8bd", kill_on_drop: false }`
[INFO] [stdout] 00a34cab348b90c3c10f5f97f7e9783b78d1f677ebde9b94e8feab41b974b8bd
