[INFO] fetching crate cmdpack 0.1.2... [INFO] checking cmdpack-0.1.2 against master#cf38b8e663f15db10ce49d7bbce02c99fc3dbc0c for pr-143170 [INFO] extracting crate cmdpack 0.1.2 into /workspace/builds/worker-0-tc1/source [INFO] started tweaking crates.io crate cmdpack 0.1.2 [INFO] finished tweaking crates.io crate cmdpack 0.1.2 [INFO] tweaked toml for crates.io crate cmdpack 0.1.2 written to /workspace/builds/worker-0-tc1/source/Cargo.toml [INFO] validating manifest of crates.io crate cmdpack 0.1.2 on toolchain cf38b8e663f15db10ce49d7bbce02c99fc3dbc0c [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+cf38b8e663f15db10ce49d7bbce02c99fc3dbc0c" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+cf38b8e663f15db10ce49d7bbce02c99fc3dbc0c" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating crates.io index [INFO] [stderr] Locking 66 packages to latest compatible versions [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+cf38b8e663f15db10ce49d7bbce02c99fc3dbc0c" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded extlog v0.1.12 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc1/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:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+cf38b8e663f15db10ce49d7bbce02c99fc3dbc0c" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 6b09cafb4986599e13cece04df7a595a2486db76f71b9415984d4e7bc8b6b9c0 [INFO] running `Command { std: "docker" "start" "-a" "6b09cafb4986599e13cece04df7a595a2486db76f71b9415984d4e7bc8b6b9c0", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "6b09cafb4986599e13cece04df7a595a2486db76f71b9415984d4e7bc8b6b9c0", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "6b09cafb4986599e13cece04df7a595a2486db76f71b9415984d4e7bc8b6b9c0", kill_on_drop: false }` [INFO] [stdout] 6b09cafb4986599e13cece04df7a595a2486db76f71b9415984d4e7bc8b6b9c0 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc1/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:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+cf38b8e663f15db10ce49d7bbce02c99fc3dbc0c" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] bf75074590948c978d5628e5e146ab21f1477edf636c6c4a96786f1475b94156 [INFO] running `Command { std: "docker" "start" "-a" "bf75074590948c978d5628e5e146ab21f1477edf636c6c4a96786f1475b94156", kill_on_drop: false }` [INFO] [stderr] Compiling num-traits v0.2.19 [INFO] [stderr] Compiling proc-macro2 v1.0.95 [INFO] [stderr] Compiling indexmap v1.9.3 [INFO] [stderr] Checking linked-hash-map v0.5.6 [INFO] [stderr] Checking hashbrown v0.12.3 [INFO] [stderr] Checking traitobject v0.1.1 [INFO] [stderr] Checking log v0.4.27 [INFO] [stderr] Checking arc-swap v0.3.11 [INFO] [stderr] Checking antidote v1.0.0 [INFO] [stderr] Checking log-mdc v0.1.0 [INFO] [stderr] Checking serde_json v1.0.140 [INFO] [stderr] Checking thread-id v3.3.0 [INFO] [stderr] Checking unsafe-any v0.4.2 [INFO] [stderr] Checking typemap v0.3.3 [INFO] [stderr] Checking yaml-rust v0.4.5 [INFO] [stderr] Compiling quote v1.0.40 [INFO] [stderr] Compiling syn v2.0.104 [INFO] [stderr] Checking ordered-float v1.1.1 [INFO] [stderr] Checking chrono v0.4.41 [INFO] [stderr] Checking serde_yaml v0.8.26 [INFO] [stderr] Checking serde-value v0.5.3 [INFO] [stderr] Compiling serde_derive v1.0.219 [INFO] [stderr] Checking log4rs v0.8.3 [INFO] [stderr] Checking extlog v0.1.12 [INFO] [stderr] Checking cmdpack v0.1.2 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stdout] --> src/lib.rs:107:5 [INFO] [stdout] | [INFO] [stdout] 107 | debug_buffer_trace!(inputb.as_ptr(),512,"write out buffer top [512]"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `format_buffer_log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `format_buffer_log` may come from an old version of the `extlog` crate, try updating your dependency with `cargo update -p extlog` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `format_buffer_log` which comes from the expansion of the macro `debug_buffer_trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stdout] --> src/lib.rs:107:5 [INFO] [stdout] | [INFO] [stdout] 107 | debug_buffer_trace!(inputb.as_ptr(),512,"write out buffer top [512]"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `format_buffer_log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `format_buffer_log` may come from an old version of the `extlog` crate, try updating your dependency with `cargo update -p extlog` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `format_buffer_log` which comes from the expansion of the macro `debug_buffer_trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stdout] --> src/lib.rs:107:5 [INFO] [stdout] | [INFO] [stdout] 107 | debug_buffer_trace!(inputb.as_ptr(),512,"write out buffer top [512]"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `format_buffer_log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `format_buffer_log` may come from an old version of the `extlog` crate, try updating your dependency with `cargo update -p extlog` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `format_buffer_log` which comes from the expansion of the macro `debug_buffer_trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stdout] --> src/lib.rs:108:5 [INFO] [stdout] | [INFO] [stdout] 108 | debug_buffer_trace!(inputb[(inputb.len()-512)..].as_ptr(),512,"write out buffer end [512]"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `format_buffer_log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `format_buffer_log` may come from an old version of the `extlog` crate, try updating your dependency with `cargo update -p extlog` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `format_buffer_log` which comes from the expansion of the macro `debug_buffer_trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stdout] --> src/lib.rs:108:5 [INFO] [stdout] | [INFO] [stdout] 108 | debug_buffer_trace!(inputb[(inputb.len()-512)..].as_ptr(),512,"write out buffer end [512]"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `format_buffer_log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `format_buffer_log` may come from an old version of the `extlog` crate, try updating your dependency with `cargo update -p extlog` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `format_buffer_log` which comes from the expansion of the macro `debug_buffer_trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stdout] --> src/lib.rs:110:5 [INFO] [stdout] | [INFO] [stdout] 110 | debug_buffer_trace!(inputb.as_ptr(),inputb.len(),"write out buffer"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `format_buffer_log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `format_buffer_log` may come from an old version of the `extlog` crate, try updating your dependency with `cargo update -p extlog` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `format_buffer_log` which comes from the expansion of the macro `debug_buffer_trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stdout] --> src/lib.rs:110:5 [INFO] [stdout] | [INFO] [stdout] 110 | debug_buffer_trace!(inputb.as_ptr(),inputb.len(),"write out buffer"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `format_buffer_log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `format_buffer_log` may come from an old version of the `extlog` crate, try updating your dependency with `cargo update -p extlog` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `format_buffer_log` which comes from the expansion of the macro `debug_buffer_trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stdout] --> src/lib.rs:122:6 [INFO] [stdout] | [INFO] [stdout] 122 | debug_trace!("writed {}:0x{:x}",writed,writed); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `format_str_log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `format_str_log` may come from an old version of the `extlog` crate, try updating your dependency with `cargo update -p extlog` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `format_str_log` which comes from the expansion of the macro `debug_trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stdout] --> src/lib.rs:122:6 [INFO] [stdout] | [INFO] [stdout] 122 | debug_trace!("writed {}:0x{:x}",writed,writed); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `format_str_log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `format_str_log` may come from an old version of the `extlog` crate, try updating your dependency with `cargo update -p extlog` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `format_str_log` which comes from the expansion of the macro `debug_trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stdout] --> src/lib.rs:129:6 [INFO] [stdout] | [INFO] [stdout] 129 | debug_trace!("write {}:0x{:x} size",cursize,cursize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `format_str_log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `format_str_log` may come from an old version of the `extlog` crate, try updating your dependency with `cargo update -p extlog` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `format_str_log` which comes from the expansion of the macro `debug_trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stdout] --> src/lib.rs:129:6 [INFO] [stdout] | [INFO] [stdout] 129 | debug_trace!("write {}:0x{:x} size",cursize,cursize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `format_str_log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `format_str_log` may come from an old version of the `extlog` crate, try updating your dependency with `cargo update -p extlog` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `format_str_log` which comes from the expansion of the macro `debug_trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stdout] --> src/lib.rs:107:5 [INFO] [stdout] | [INFO] [stdout] 107 | debug_buffer_trace!(inputb.as_ptr(),512,"write out buffer top [512]"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `format_buffer_log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `format_buffer_log` may come from an old version of the `extlog` crate, try updating your dependency with `cargo update -p extlog` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `format_buffer_log` which comes from the expansion of the macro `debug_buffer_trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stdout] --> src/lib.rs:108:5 [INFO] [stdout] | [INFO] [stdout] 108 | debug_buffer_trace!(inputb[(inputb.len()-512)..].as_ptr(),512,"write out buffer end [512]"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `format_buffer_log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `format_buffer_log` may come from an old version of the `extlog` crate, try updating your dependency with `cargo update -p extlog` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `format_buffer_log` which comes from the expansion of the macro `debug_buffer_trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stdout] --> src/lib.rs:108:5 [INFO] [stdout] | [INFO] [stdout] 108 | debug_buffer_trace!(inputb[(inputb.len()-512)..].as_ptr(),512,"write out buffer end [512]"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `format_buffer_log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `format_buffer_log` may come from an old version of the `extlog` crate, try updating your dependency with `cargo update -p extlog` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `format_buffer_log` which comes from the expansion of the macro `debug_buffer_trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stdout] --> src/lib.rs:110:5 [INFO] [stdout] | [INFO] [stdout] 110 | debug_buffer_trace!(inputb.as_ptr(),inputb.len(),"write out buffer"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `format_buffer_log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `format_buffer_log` may come from an old version of the `extlog` crate, try updating your dependency with `cargo update -p extlog` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `format_buffer_log` which comes from the expansion of the macro `debug_buffer_trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stdout] --> src/lib.rs:110:5 [INFO] [stdout] | [INFO] [stdout] 110 | debug_buffer_trace!(inputb.as_ptr(),inputb.len(),"write out buffer"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `format_buffer_log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `format_buffer_log` may come from an old version of the `extlog` crate, try updating your dependency with `cargo update -p extlog` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `format_buffer_log` which comes from the expansion of the macro `debug_buffer_trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stdout] --> src/lib.rs:122:6 [INFO] [stdout] | [INFO] [stdout] 122 | debug_trace!("writed {}:0x{:x}",writed,writed); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `format_str_log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `format_str_log` may come from an old version of the `extlog` crate, try updating your dependency with `cargo update -p extlog` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `format_str_log` which comes from the expansion of the macro `debug_trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stdout] --> src/lib.rs:122:6 [INFO] [stdout] | [INFO] [stdout] 122 | debug_trace!("writed {}:0x{:x}",writed,writed); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `format_str_log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `format_str_log` may come from an old version of the `extlog` crate, try updating your dependency with `cargo update -p extlog` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `format_str_log` which comes from the expansion of the macro `debug_trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stdout] --> src/lib.rs:129:6 [INFO] [stdout] | [INFO] [stdout] 129 | debug_trace!("write {}:0x{:x} size",cursize,cursize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `format_str_log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `format_str_log` may come from an old version of the `extlog` crate, try updating your dependency with `cargo update -p extlog` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `format_str_log` which comes from the expansion of the macro `debug_trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stdout] --> src/lib.rs:129:6 [INFO] [stdout] | [INFO] [stdout] 129 | debug_trace!("write {}:0x{:x} size",cursize,cursize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `format_str_log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `format_str_log` may come from an old version of the `extlog` crate, try updating your dependency with `cargo update -p extlog` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `format_str_log` which comes from the expansion of the macro `debug_trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stdout] --> src/lib.rs:193:3 [INFO] [stdout] | [INFO] [stdout] 193 | debug_trace!("CmdExec close"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `format_str_log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `format_str_log` may come from an old version of the `extlog` crate, try updating your dependency with `cargo update -p extlog` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `format_str_log` which comes from the expansion of the macro `debug_trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stdout] --> src/lib.rs:193:3 [INFO] [stdout] | [INFO] [stdout] 193 | debug_trace!("CmdExec close"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `format_str_log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `format_str_log` may come from an old version of the `extlog` crate, try updating your dependency with `cargo update -p extlog` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `format_str_log` which comes from the expansion of the macro `debug_trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stdout] --> src/lib.rs:193:3 [INFO] [stdout] | [INFO] [stdout] 193 | debug_trace!("CmdExec close"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `format_str_log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `format_str_log` may come from an old version of the `extlog` crate, try updating your dependency with `cargo update -p extlog` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `format_str_log` which comes from the expansion of the macro `debug_trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stdout] --> src/lib.rs:193:3 [INFO] [stdout] | [INFO] [stdout] 193 | debug_trace!("CmdExec close"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `format_str_log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `format_str_log` may come from an old version of the `extlog` crate, try updating your dependency with `cargo update -p extlog` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `format_str_log` which comes from the expansion of the macro `debug_trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 10.80s [INFO] [stderr] warning: the following packages contain code that will be rejected by a future version of Rust: typemap v0.3.3 [INFO] [stderr] note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 1` [INFO] running `Command { std: "docker" "inspect" "bf75074590948c978d5628e5e146ab21f1477edf636c6c4a96786f1475b94156", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "bf75074590948c978d5628e5e146ab21f1477edf636c6c4a96786f1475b94156", kill_on_drop: false }` [INFO] [stdout] bf75074590948c978d5628e5e146ab21f1477edf636c6c4a96786f1475b94156