[INFO] fetching crate cmdpack 0.1.2... [INFO] testing cmdpack-0.1.2 against try#8de4c7234dd9b97c9d76b58671343fdbbc9a433e+target=x86_64-unknown-linux-musl for musl_upgrade_1_2_5_with_libc_patch_0 [INFO] extracting crate cmdpack 0.1.2 into /workspace/builds/worker-3-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-3-tc1/source/Cargo.toml [INFO] validating manifest of crates.io crate cmdpack 0.1.2 on toolchain 8de4c7234dd9b97c9d76b58671343fdbbc9a433e [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "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" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Updating crates.io index [INFO] [stderr] Blocking waiting for file lock on package cache [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" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "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 serde-value v0.5.3 [INFO] [stderr] Downloaded extlog v0.1.12 [INFO] [stderr] Downloaded arc-swap v0.3.11 [INFO] [stderr] Downloaded log4rs v0.8.3 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-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" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 3ddabde218788aec4fcbaa5a98bebc5b0146d9b7dfae4d61cabd1cb7c60d206f [INFO] running `Command { std: "docker" "start" "-a" "3ddabde218788aec4fcbaa5a98bebc5b0146d9b7dfae4d61cabd1cb7c60d206f", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "3ddabde218788aec4fcbaa5a98bebc5b0146d9b7dfae4d61cabd1cb7c60d206f", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "3ddabde218788aec4fcbaa5a98bebc5b0146d9b7dfae4d61cabd1cb7c60d206f", kill_on_drop: false }` [INFO] [stdout] 3ddabde218788aec4fcbaa5a98bebc5b0146d9b7dfae4d61cabd1cb7c60d206f [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-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" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "build" "--frozen" "--message-format=json" "--target" "x86_64-unknown-linux-musl", kill_on_drop: false }` [INFO] [stdout] 770bdfdcd128088f3b8d1340c8834e2f53973a586fedfed654c300ace6b1ef23 [INFO] running `Command { std: "docker" "start" "-a" "770bdfdcd128088f3b8d1340c8834e2f53973a586fedfed654c300ace6b1ef23", kill_on_drop: false }` [INFO] [stderr] Compiling serde v1.0.219 [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] Compiling hashbrown v0.12.3 [INFO] [stderr] Compiling traitobject v0.1.1 [INFO] [stderr] Compiling adler2 v2.0.1 [INFO] [stderr] Compiling memchr v2.7.5 [INFO] [stderr] Compiling iana-time-zone v0.1.63 [INFO] [stderr] Compiling yaml-rust v0.4.5 [INFO] [stderr] Compiling crc32fast v1.4.2 [INFO] [stderr] Compiling humantime v1.3.0 [INFO] [stderr] Compiling antidote v1.0.0 [INFO] [stderr] Compiling log-mdc v0.1.0 [INFO] [stderr] Compiling arc-swap v0.3.11 [INFO] [stderr] Compiling thread-id v3.3.0 [INFO] [stderr] Compiling unsafe-any v0.4.2 [INFO] [stderr] Compiling miniz_oxide v0.8.9 [INFO] [stderr] Compiling typemap v0.3.3 [INFO] [stderr] Compiling flate2 v1.1.2 [INFO] [stderr] Compiling quote v1.0.40 [INFO] [stderr] Compiling ordered-float v1.1.1 [INFO] [stderr] Compiling chrono v0.4.41 [INFO] [stderr] Compiling syn v2.0.104 [INFO] [stderr] Compiling serde_yaml v0.8.26 [INFO] [stderr] Compiling serde-value v0.5.3 [INFO] [stderr] Compiling log v0.4.27 [INFO] [stderr] Compiling serde_json v1.0.140 [INFO] [stderr] Compiling serde_derive v1.0.219 [INFO] [stderr] Compiling log4rs v0.8.3 [INFO] [stderr] Compiling extlog v0.1.12 [INFO] [stderr] Compiling 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: 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] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 15.25s [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 2` [INFO] running `Command { std: "docker" "inspect" "770bdfdcd128088f3b8d1340c8834e2f53973a586fedfed654c300ace6b1ef23", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "770bdfdcd128088f3b8d1340c8834e2f53973a586fedfed654c300ace6b1ef23", kill_on_drop: false }` [INFO] [stdout] 770bdfdcd128088f3b8d1340c8834e2f53973a586fedfed654c300ace6b1ef23 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-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" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "test" "--frozen" "--no-run" "--message-format=json" "--target" "x86_64-unknown-linux-musl", kill_on_drop: false }` [INFO] [stdout] b654ceea2edfa625fac32c6579a92db4903e563da8d65ca047d29af68db935df [INFO] running `Command { std: "docker" "start" "-a" "b654ceea2edfa625fac32c6579a92db4903e563da8d65ca047d29af68db935df", kill_on_drop: false }` [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: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] Compiling 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: 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] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 0.72s [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 2` [INFO] running `Command { std: "docker" "inspect" "b654ceea2edfa625fac32c6579a92db4903e563da8d65ca047d29af68db935df", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "b654ceea2edfa625fac32c6579a92db4903e563da8d65ca047d29af68db935df", kill_on_drop: false }` [INFO] [stdout] b654ceea2edfa625fac32c6579a92db4903e563da8d65ca047d29af68db935df [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-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" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "test" "--frozen" "--target" "x86_64-unknown-linux-musl", kill_on_drop: false }` [INFO] [stdout] e5cca7848141018ed25db4a107185fcac57de0c7dcc1246c9beaa3e10e1bc6fc [INFO] running `Command { std: "docker" "start" "-a" "e5cca7848141018ed25db4a107185fcac57de0c7dcc1246c9beaa3e10e1bc6fc", kill_on_drop: false }` [INFO] [stderr] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stderr] --> src/lib.rs:107:5 [INFO] [stderr] | [INFO] [stderr] 107 | debug_buffer_trace!(inputb.as_ptr(),512,"write out buffer top [512]"); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `format_buffer_log` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] = 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] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stderr] --> src/lib.rs:107:5 [INFO] [stderr] | [INFO] [stderr] 107 | debug_buffer_trace!(inputb.as_ptr(),512,"write out buffer top [512]"); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `format_buffer_log` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = 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] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stderr] --> src/lib.rs:108:5 [INFO] [stderr] | [INFO] [stderr] 108 | debug_buffer_trace!(inputb[(inputb.len()-512)..].as_ptr(),512,"write out buffer end [512]"); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `format_buffer_log` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = 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] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stderr] --> src/lib.rs:110:5 [INFO] [stderr] | [INFO] [stderr] 110 | debug_buffer_trace!(inputb.as_ptr(),inputb.len(),"write out buffer"); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `format_buffer_log` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = 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] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stderr] --> src/lib.rs:122:6 [INFO] [stderr] | [INFO] [stderr] 122 | debug_trace!("writed {}:0x{:x}",writed,writed); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `format_str_log` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = 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] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stderr] --> src/lib.rs:129:6 [INFO] [stderr] | [INFO] [stderr] 129 | debug_trace!("write {}:0x{:x} size",cursize,cursize); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `format_str_log` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = 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] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `longname_mode` [INFO] [stderr] --> src/lib.rs:193:3 [INFO] [stderr] | [INFO] [stderr] 193 | debug_trace!("CmdExec close"); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `format_str_log` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = 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] [stderr] [INFO] [stderr] warning: `cmdpack` (lib) generated 12 warnings (5 duplicates) [INFO] [stderr] warning: `cmdpack` (lib test) generated 12 warnings (12 duplicates) [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 0.16s [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 2` [INFO] [stdout] [INFO] [stderr] Running unittests src/lib.rs (/opt/rustwide/target/x86_64-unknown-linux-musl/debug/deps/cmdpack-0573ada8b966a471) [INFO] [stdout] running 0 tests [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stdout] [INFO] running `Command { std: "docker" "inspect" "e5cca7848141018ed25db4a107185fcac57de0c7dcc1246c9beaa3e10e1bc6fc", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "e5cca7848141018ed25db4a107185fcac57de0c7dcc1246c9beaa3e10e1bc6fc", kill_on_drop: false }` [INFO] [stdout] e5cca7848141018ed25db4a107185fcac57de0c7dcc1246c9beaa3e10e1bc6fc