[INFO] fetching crate cmdpack 0.1.2...
[INFO] testing cmdpack-0.1.2 against 1.90.0 for beta-1.91-3
[INFO] extracting crate cmdpack 0.1.2 into /workspace/builds/worker-2-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-2-tc1/source/Cargo.toml
[INFO] validating manifest of crates.io crate cmdpack 0.1.2 on toolchain 1.90.0
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+1.90.0" "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" "+1.90.0" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 67 packages to latest compatible versions
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+1.90.0" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded traitobject v0.1.1
[INFO] [stderr]   Downloaded serde-value v0.5.3
[INFO] [stderr]   Downloaded thread-id v3.3.0
[INFO] [stderr]   Downloaded extlog v0.1.12
[INFO] [stderr]   Downloaded log4rs v0.8.3
[INFO] [stderr]   Downloaded log-mdc v0.1.0
[INFO] [stderr]   Downloaded ordered-float v1.1.1
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-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:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+1.90.0" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] a2e1ac50b3a748b6a6d2f14ec8a3dce48820ba6aba8a34d23d083f372e5f738f
[INFO] running `Command { std: "docker" "start" "-a" "a2e1ac50b3a748b6a6d2f14ec8a3dce48820ba6aba8a34d23d083f372e5f738f", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "a2e1ac50b3a748b6a6d2f14ec8a3dce48820ba6aba8a34d23d083f372e5f738f", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "a2e1ac50b3a748b6a6d2f14ec8a3dce48820ba6aba8a34d23d083f372e5f738f", kill_on_drop: false }`
[INFO] [stdout] a2e1ac50b3a748b6a6d2f14ec8a3dce48820ba6aba8a34d23d083f372e5f738f
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-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=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-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:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+1.90.0" "build" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] c4ace8122760291dbe04d54a0b4cf9962dd531ada2fbef213d13b4ef30e6ff41
[INFO] running `Command { std: "docker" "start" "-a" "c4ace8122760291dbe04d54a0b4cf9962dd531ada2fbef213d13b4ef30e6ff41", kill_on_drop: false }`
[INFO] [stderr]    Compiling serde_core v1.0.228
[INFO] [stderr]    Compiling num-traits v0.2.19
[INFO] [stderr]    Compiling serde v1.0.228
[INFO] [stderr]    Compiling quote v1.0.41
[INFO] [stderr]    Compiling indexmap v1.9.3
[INFO] [stderr]    Compiling linked-hash-map v0.5.6
[INFO] [stderr]    Compiling traitobject v0.1.1
[INFO] [stderr]    Compiling serde_json v1.0.145
[INFO] [stderr]    Compiling proc-macro2 v1.0.101
[INFO] [stderr]    Compiling memchr v2.7.6
[INFO] [stderr]    Compiling crc32fast v1.5.0
[INFO] [stderr]    Compiling antidote v1.0.0
[INFO] [stderr]    Compiling log-mdc v0.1.0
[INFO] [stderr]    Compiling thread-id v3.3.0
[INFO] [stderr]    Compiling arc-swap v0.3.11
[INFO] [stderr]    Compiling unsafe-any v0.4.2
[INFO] [stderr]    Compiling flate2 v1.1.2
[INFO] [stderr]    Compiling yaml-rust v0.4.5
[INFO] [stderr]    Compiling typemap v0.3.3
[INFO] [stderr]    Compiling syn v2.0.106
[INFO] [stderr]    Compiling ordered-float v1.1.1
[INFO] [stderr]    Compiling chrono v0.4.42
[INFO] [stderr]    Compiling serde_derive v1.0.228
[INFO] [stderr]    Compiling serde_yaml v0.8.26
[INFO] [stderr]    Compiling serde-value v0.5.3
[INFO] [stderr]    Compiling log v0.4.28
[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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]     = 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 11.18s
[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 5`
[INFO] running `Command { std: "docker" "inspect" "c4ace8122760291dbe04d54a0b4cf9962dd531ada2fbef213d13b4ef30e6ff41", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "c4ace8122760291dbe04d54a0b4cf9962dd531ada2fbef213d13b4ef30e6ff41", kill_on_drop: false }`
[INFO] [stdout] c4ace8122760291dbe04d54a0b4cf9962dd531ada2fbef213d13b4ef30e6ff41
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-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=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-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:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+1.90.0" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 93fe4e8a4998acd1ee90630007d81fc44446441f69b1f547d6828f085223f111
[INFO] running `Command { std: "docker" "start" "-a" "93fe4e8a4998acd1ee90630007d81fc44446441f69b1f547d6828f085223f111", 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]     = 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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: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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]     = 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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.49s
[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 5`
[INFO] running `Command { std: "docker" "inspect" "93fe4e8a4998acd1ee90630007d81fc44446441f69b1f547d6828f085223f111", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "93fe4e8a4998acd1ee90630007d81fc44446441f69b1f547d6828f085223f111", kill_on_drop: false }`
[INFO] [stdout] 93fe4e8a4998acd1ee90630007d81fc44446441f69b1f547d6828f085223f111
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-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=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-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:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+1.90.0" "test" "--frozen", kill_on_drop: false }`
[INFO] [stdout] 9311233b30b93fe95b586cccf40bc1c0416c76f6d58efb590e85035d77ed2241
[INFO] running `Command { std: "docker" "start" "-a" "9311233b30b93fe95b586cccf40bc1c0416c76f6d58efb590e85035d77ed2241", 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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.09s
[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 5`
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/cmdpack-c9b2d4f389cc0eb2)
[INFO] [stderr]    Doc-tests cmdpack
[INFO] [stdout] 
[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] [stdout] 
[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" "9311233b30b93fe95b586cccf40bc1c0416c76f6d58efb590e85035d77ed2241", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "9311233b30b93fe95b586cccf40bc1c0416c76f6d58efb590e85035d77ed2241", kill_on_drop: false }`
[INFO] [stdout] 9311233b30b93fe95b586cccf40bc1c0416c76f6d58efb590e85035d77ed2241
