[INFO] fetching crate error-chain 0.12.4... [INFO] testing error-chain-0.12.4 against 1.90.0 for beta-1.91-3 [INFO] extracting crate error-chain 0.12.4 into /workspace/builds/worker-3-tc1/source [INFO] started tweaking crates.io crate error-chain 0.12.4 [INFO] finished tweaking crates.io crate error-chain 0.12.4 [INFO] tweaked toml for crates.io crate error-chain 0.12.4 written to /workspace/builds/worker-3-tc1/source/Cargo.toml [INFO] validating manifest of crates.io crate error-chain 0.12.4 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] crate crates.io crate error-chain 0.12.4 already has a lockfile, it will not be regenerated [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] warning: no edition set: defaulting to the 2015 edition while the latest is 2024 [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded backtrace v0.3.48 [INFO] [stderr] Downloaded addr2line v0.12.1 [INFO] [stderr] Downloaded object v0.19.0 [INFO] [stderr] Downloaded gimli v0.21.0 [INFO] [stderr] Downloaded libc v0.2.71 [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:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+1.90.0" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] b8d1e81c0287387421a78bdc4bc06d5f4f320b4950a7af06e5c6c875e007382a [INFO] running `Command { std: "docker" "start" "-a" "b8d1e81c0287387421a78bdc4bc06d5f4f320b4950a7af06e5c6c875e007382a", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "b8d1e81c0287387421a78bdc4bc06d5f4f320b4950a7af06e5c6c875e007382a", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "b8d1e81c0287387421a78bdc4bc06d5f4f320b4950a7af06e5c6c875e007382a", kill_on_drop: false }` [INFO] [stdout] b8d1e81c0287387421a78bdc4bc06d5f4f320b4950a7af06e5c6c875e007382a [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=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] 19a15e4db867f41453c7da40271b36f94665346f8696e078c74dac549b864444 [INFO] running `Command { std: "docker" "start" "-a" "19a15e4db867f41453c7da40271b36f94665346f8696e078c74dac549b864444", kill_on_drop: false }` [INFO] [stderr] warning: no edition set: defaulting to the 2015 edition while the latest is 2024 [INFO] [stderr] Compiling libc v0.2.71 [INFO] [stderr] Compiling gimli v0.21.0 [INFO] [stderr] Compiling error-chain v0.12.4 (/opt/rustwide/workdir) [INFO] [stderr] Compiling object v0.19.0 [INFO] [stderr] Compiling addr2line v0.12.1 [INFO] [stderr] Compiling backtrace v0.3.48 [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stdout] --> src/error_chain.rs:3:11 [INFO] [stdout] | [INFO] [stdout] 3 | #[cfg(not(has_error_source))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stdout] --> src/error_chain.rs:36:7 [INFO] [stdout] | [INFO] [stdout] 36 | #[cfg(has_error_source)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> src/error_chain.rs:73:7 [INFO] [stdout] | [INFO] [stdout] 73 | #[cfg(has_error_description_deprecated)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> src/error_chain.rs:82:11 [INFO] [stdout] | [INFO] [stdout] 82 | #[cfg(not(has_error_description_deprecated))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> src/error_chain.rs:323:23 [INFO] [stdout] | [INFO] [stdout] 323 | #[cfg(not(has_error_description_deprecated))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/example_generated.rs:24:5 [INFO] [stdout] | [INFO] [stdout] 24 | error_chain! {} [INFO] [stdout] | --------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> src/error_chain.rs:323:23 [INFO] [stdout] | [INFO] [stdout] 323 | #[cfg(not(has_error_description_deprecated))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/example_generated.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | / error_chain! { [INFO] [stdout] 28 | | links { [INFO] [stdout] 29 | | Inner(inner::Error, inner::ErrorKind) #[doc = "Link to another `ErrorChain`."]; [INFO] [stdout] ... | [INFO] [stdout] 38 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stdout] --> src/lib.rs:581:31 [INFO] [stdout] | [INFO] [stdout] 581 | #[cfg(not(has_error_source))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stdout] --> src/lib.rs:583:27 [INFO] [stdout] | [INFO] [stdout] 583 | #[cfg(has_error_source)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> src/error_chain.rs:323:23 [INFO] [stdout] | [INFO] [stdout] 323 | #[cfg(not(has_error_description_deprecated))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/lib.rs:823:5 [INFO] [stdout] | [INFO] [stdout] 823 | error_chain! {} [INFO] [stdout] | --------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/lib.rs:615:13 [INFO] [stdout] | [INFO] [stdout] 615 | fn iter(&self) -> Iter; [INFO] [stdout] | ^^^^^ ---- the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 615 | fn iter(&self) -> Iter<'_>; [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error_chain.rs:244:21 [INFO] [stdout] | [INFO] [stdout] 244 | fn iter(&self) -> $crate::Iter { [INFO] [stdout] | ^^^^^ ------------ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] ::: src/example_generated.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | / error_chain! { [INFO] [stdout] 28 | | links { [INFO] [stdout] 29 | | Inner(inner::Error, inner::ErrorKind) #[doc = "Link to another `ErrorChain`."]; [INFO] [stdout] ... | [INFO] [stdout] 38 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 244 | fn iter(&self) -> $crate::Iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error_chain.rs:300:25 [INFO] [stdout] | [INFO] [stdout] 300 | pub fn iter(&self) -> $crate::Iter { [INFO] [stdout] | ^^^^^ ------------ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] ::: src/example_generated.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | / error_chain! { [INFO] [stdout] 28 | | links { [INFO] [stdout] 29 | | Inner(inner::Error, inner::ErrorKind) #[doc = "Link to another `ErrorChain`."]; [INFO] [stdout] ... | [INFO] [stdout] 38 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 300 | pub fn iter(&self) -> $crate::Iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error_chain.rs:244:21 [INFO] [stdout] | [INFO] [stdout] 244 | fn iter(&self) -> $crate::Iter { [INFO] [stdout] | ^^^^^ ------------ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] ::: src/example_generated.rs:24:5 [INFO] [stdout] | [INFO] [stdout] 24 | error_chain! {} [INFO] [stdout] | --------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 244 | fn iter(&self) -> $crate::Iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error_chain.rs:300:25 [INFO] [stdout] | [INFO] [stdout] 300 | pub fn iter(&self) -> $crate::Iter { [INFO] [stdout] | ^^^^^ ------------ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] ::: src/example_generated.rs:24:5 [INFO] [stdout] | [INFO] [stdout] 24 | error_chain! {} [INFO] [stdout] | --------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 300 | pub fn iter(&self) -> $crate::Iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error_chain.rs:244:21 [INFO] [stdout] | [INFO] [stdout] 244 | fn iter(&self) -> $crate::Iter { [INFO] [stdout] | ^^^^^ ------------ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] ::: src/lib.rs:823:5 [INFO] [stdout] | [INFO] [stdout] 823 | error_chain! {} [INFO] [stdout] | --------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 244 | fn iter(&self) -> $crate::Iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error_chain.rs:300:25 [INFO] [stdout] | [INFO] [stdout] 300 | pub fn iter(&self) -> $crate::Iter { [INFO] [stdout] | ^^^^^ ------------ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] ::: src/lib.rs:823:5 [INFO] [stdout] | [INFO] [stdout] 823 | error_chain! {} [INFO] [stdout] | --------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 300 | pub fn iter(&self) -> $crate::Iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 4.12s [INFO] running `Command { std: "docker" "inspect" "19a15e4db867f41453c7da40271b36f94665346f8696e078c74dac549b864444", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "19a15e4db867f41453c7da40271b36f94665346f8696e078c74dac549b864444", kill_on_drop: false }` [INFO] [stdout] 19a15e4db867f41453c7da40271b36f94665346f8696e078c74dac549b864444 [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=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] 70e739f5497b345f37e733f04aa3b9b7b91502f64e9c246ff7e05d0cc1a9ec29 [INFO] running `Command { std: "docker" "start" "-a" "70e739f5497b345f37e733f04aa3b9b7b91502f64e9c246ff7e05d0cc1a9ec29", kill_on_drop: false }` [INFO] [stderr] warning: no edition set: defaulting to the 2015 edition while the latest is 2024 [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stdout] --> src/error_chain.rs:3:11 [INFO] [stdout] | [INFO] [stdout] 3 | #[cfg(not(has_error_source))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stdout] --> src/error_chain.rs:36:7 [INFO] [stdout] | [INFO] [stdout] 36 | #[cfg(has_error_source)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> src/error_chain.rs:73:7 [INFO] [stdout] | [INFO] [stdout] 73 | #[cfg(has_error_description_deprecated)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> src/error_chain.rs:82:11 [INFO] [stdout] | [INFO] [stdout] 82 | #[cfg(not(has_error_description_deprecated))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> src/error_chain.rs:323:23 [INFO] [stdout] | [INFO] [stdout] 323 | #[cfg(not(has_error_description_deprecated))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/example_generated.rs:24:5 [INFO] [stdout] | [INFO] [stdout] 24 | error_chain! {} [INFO] [stdout] | --------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> src/error_chain.rs:323:23 [INFO] [stdout] | [INFO] [stdout] 323 | #[cfg(not(has_error_description_deprecated))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/example_generated.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | / error_chain! { [INFO] [stdout] 28 | | links { [INFO] [stdout] 29 | | Inner(inner::Error, inner::ErrorKind) #[doc = "Link to another `ErrorChain`."]; [INFO] [stdout] ... | [INFO] [stdout] 38 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stdout] --> src/lib.rs:581:31 [INFO] [stdout] | [INFO] [stdout] 581 | #[cfg(not(has_error_source))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stdout] --> src/lib.rs:583:27 [INFO] [stdout] | [INFO] [stdout] 583 | #[cfg(has_error_source)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> src/error_chain.rs:323:23 [INFO] [stdout] | [INFO] [stdout] 323 | #[cfg(not(has_error_description_deprecated))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/lib.rs:823:5 [INFO] [stdout] | [INFO] [stdout] 823 | error_chain! {} [INFO] [stdout] | --------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/lib.rs:615:13 [INFO] [stdout] | [INFO] [stdout] 615 | fn iter(&self) -> Iter; [INFO] [stdout] | ^^^^^ ---- the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 615 | fn iter(&self) -> Iter<'_>; [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error_chain.rs:244:21 [INFO] [stdout] | [INFO] [stdout] 244 | fn iter(&self) -> $crate::Iter { [INFO] [stdout] | ^^^^^ ------------ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] ::: src/example_generated.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | / error_chain! { [INFO] [stdout] 28 | | links { [INFO] [stdout] 29 | | Inner(inner::Error, inner::ErrorKind) #[doc = "Link to another `ErrorChain`."]; [INFO] [stdout] ... | [INFO] [stdout] 38 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 244 | fn iter(&self) -> $crate::Iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error_chain.rs:300:25 [INFO] [stdout] | [INFO] [stdout] 300 | pub fn iter(&self) -> $crate::Iter { [INFO] [stdout] | ^^^^^ ------------ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] ::: src/example_generated.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | / error_chain! { [INFO] [stdout] 28 | | links { [INFO] [stdout] 29 | | Inner(inner::Error, inner::ErrorKind) #[doc = "Link to another `ErrorChain`."]; [INFO] [stdout] ... | [INFO] [stdout] 38 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 300 | pub fn iter(&self) -> $crate::Iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error_chain.rs:244:21 [INFO] [stdout] | [INFO] [stdout] 244 | fn iter(&self) -> $crate::Iter { [INFO] [stdout] | ^^^^^ ------------ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] ::: src/example_generated.rs:24:5 [INFO] [stdout] | [INFO] [stdout] 24 | error_chain! {} [INFO] [stdout] | --------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 244 | fn iter(&self) -> $crate::Iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error_chain.rs:300:25 [INFO] [stdout] | [INFO] [stdout] 300 | pub fn iter(&self) -> $crate::Iter { [INFO] [stdout] | ^^^^^ ------------ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] ::: src/example_generated.rs:24:5 [INFO] [stdout] | [INFO] [stdout] 24 | error_chain! {} [INFO] [stdout] | --------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 300 | pub fn iter(&self) -> $crate::Iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error_chain.rs:244:21 [INFO] [stdout] | [INFO] [stdout] 244 | fn iter(&self) -> $crate::Iter { [INFO] [stdout] | ^^^^^ ------------ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] ::: src/lib.rs:823:5 [INFO] [stdout] | [INFO] [stdout] 823 | error_chain! {} [INFO] [stdout] | --------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 244 | fn iter(&self) -> $crate::Iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error_chain.rs:300:25 [INFO] [stdout] | [INFO] [stdout] 300 | pub fn iter(&self) -> $crate::Iter { [INFO] [stdout] | ^^^^^ ------------ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] ::: src/lib.rs:823:5 [INFO] [stdout] | [INFO] [stdout] 823 | error_chain! {} [INFO] [stdout] | --------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 300 | pub fn iter(&self) -> $crate::Iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling error-chain v0.12.4 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> examples/size.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / error_chain! { [INFO] [stdout] 7 | | errors { [INFO] [stdout] 8 | | AVariant [INFO] [stdout] 9 | | Another [INFO] [stdout] 10 | | } [INFO] [stdout] 11 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [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 `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> examples/quickstart.rs:17:5 [INFO] [stdout] | [INFO] [stdout] 17 | error_chain! {} [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [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 `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> examples/has_backtrace.rs:8:1 [INFO] [stdout] | [INFO] [stdout] 8 | / error_chain! { [INFO] [stdout] 9 | | errors { [INFO] [stdout] 10 | | MyError [INFO] [stdout] 11 | | } [INFO] [stdout] 12 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [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 `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/quick_main.rs:5:1 [INFO] [stdout] | [INFO] [stdout] 5 | error_chain!(); [INFO] [stdout] | ^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [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 `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stdout] --> src/error_chain.rs:3:11 [INFO] [stdout] | [INFO] [stdout] 3 | #[cfg(not(has_error_source))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stdout] --> src/error_chain.rs:36:7 [INFO] [stdout] | [INFO] [stdout] 36 | #[cfg(has_error_source)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> src/error_chain.rs:73:7 [INFO] [stdout] | [INFO] [stdout] 73 | #[cfg(has_error_description_deprecated)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> src/error_chain.rs:82:11 [INFO] [stdout] | [INFO] [stdout] 82 | #[cfg(not(has_error_description_deprecated))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> src/error_chain.rs:323:23 [INFO] [stdout] | [INFO] [stdout] 323 | #[cfg(not(has_error_description_deprecated))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/example_generated.rs:24:5 [INFO] [stdout] | [INFO] [stdout] 24 | error_chain! {} [INFO] [stdout] | --------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> src/error_chain.rs:323:23 [INFO] [stdout] | [INFO] [stdout] 323 | #[cfg(not(has_error_description_deprecated))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/example_generated.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | / error_chain! { [INFO] [stdout] 28 | | links { [INFO] [stdout] 29 | | Inner(inner::Error, inner::ErrorKind) #[doc = "Link to another `ErrorChain`."]; [INFO] [stdout] ... | [INFO] [stdout] 38 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stdout] --> src/lib.rs:581:31 [INFO] [stdout] | [INFO] [stdout] 581 | #[cfg(not(has_error_source))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stdout] --> src/lib.rs:583:27 [INFO] [stdout] | [INFO] [stdout] 583 | #[cfg(has_error_source)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> src/error_chain.rs:323:23 [INFO] [stdout] | [INFO] [stdout] 323 | #[cfg(not(has_error_description_deprecated))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/lib.rs:823:5 [INFO] [stdout] | [INFO] [stdout] 823 | error_chain! {} [INFO] [stdout] | --------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> examples/chain_err.rs:13:5 [INFO] [stdout] | [INFO] [stdout] 13 | / error_chain! { [INFO] [stdout] 14 | | foreign_links { [INFO] [stdout] 15 | | Io(io::Error) #[doc = "Error during IO"]; [INFO] [stdout] ... | [INFO] [stdout] 29 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [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 `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `a_feature` [INFO] [stdout] --> examples/all.rs:8:7 [INFO] [stdout] | [INFO] [stdout] 8 | #[cfg(feature = "a_feature")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `backtrace`, `default`, and `example_generated` [INFO] [stdout] = help: consider adding `a_feature` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `a_feature` [INFO] [stdout] --> examples/all.rs:27:59 [INFO] [stdout] | [INFO] [stdout] 27 | Feature(feature::Error, feature::ErrorKind) #[cfg(feature = "a_feature")]; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `backtrace`, `default`, and `example_generated` [INFO] [stdout] = help: consider adding `a_feature` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> examples/all.rs:5:5 [INFO] [stdout] | [INFO] [stdout] 5 | error_chain! {} [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> examples/all.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | / error_chain! { [INFO] [stdout] 14 | | // Types generated by the macro. If empty or absent, it defaults to [INFO] [stdout] 15 | | // Error, ErrorKind, Result; [INFO] [stdout] 16 | | types { [INFO] [stdout] ... | [INFO] [stdout] 34 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> examples/doc.rs:10:5 [INFO] [stdout] | [INFO] [stdout] 10 | error_chain! {} [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [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 `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> examples/doc.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | / error_chain! { [INFO] [stdout] 14 | | links { [INFO] [stdout] 15 | | Inner(inner::Error, inner::ErrorKind) #[doc = "Doc"]; [INFO] [stdout] ... | [INFO] [stdout] 26 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/lib.rs:615:13 [INFO] [stdout] | [INFO] [stdout] 615 | fn iter(&self) -> Iter; [INFO] [stdout] | ^^^^^ ---- the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 615 | fn iter(&self) -> Iter<'_>; [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error_chain.rs:244:21 [INFO] [stdout] | [INFO] [stdout] 244 | fn iter(&self) -> $crate::Iter { [INFO] [stdout] | ^^^^^ ------------ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] ::: src/example_generated.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | / error_chain! { [INFO] [stdout] 28 | | links { [INFO] [stdout] 29 | | Inner(inner::Error, inner::ErrorKind) #[doc = "Link to another `ErrorChain`."]; [INFO] [stdout] ... | [INFO] [stdout] 38 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 244 | fn iter(&self) -> $crate::Iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error_chain.rs:300:25 [INFO] [stdout] | [INFO] [stdout] 300 | pub fn iter(&self) -> $crate::Iter { [INFO] [stdout] | ^^^^^ ------------ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] ::: src/example_generated.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | / error_chain! { [INFO] [stdout] 28 | | links { [INFO] [stdout] 29 | | Inner(inner::Error, inner::ErrorKind) #[doc = "Link to another `ErrorChain`."]; [INFO] [stdout] ... | [INFO] [stdout] 38 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 300 | pub fn iter(&self) -> $crate::Iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error_chain.rs:244:21 [INFO] [stdout] | [INFO] [stdout] 244 | fn iter(&self) -> $crate::Iter { [INFO] [stdout] | ^^^^^ ------------ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] ::: src/example_generated.rs:24:5 [INFO] [stdout] | [INFO] [stdout] 24 | error_chain! {} [INFO] [stdout] | --------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 244 | fn iter(&self) -> $crate::Iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error_chain.rs:300:25 [INFO] [stdout] | [INFO] [stdout] 300 | pub fn iter(&self) -> $crate::Iter { [INFO] [stdout] | ^^^^^ ------------ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] ::: src/example_generated.rs:24:5 [INFO] [stdout] | [INFO] [stdout] 24 | error_chain! {} [INFO] [stdout] | --------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 300 | pub fn iter(&self) -> $crate::Iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error_chain.rs:244:21 [INFO] [stdout] | [INFO] [stdout] 244 | fn iter(&self) -> $crate::Iter { [INFO] [stdout] | ^^^^^ ------------ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] ::: src/lib.rs:823:5 [INFO] [stdout] | [INFO] [stdout] 823 | error_chain! {} [INFO] [stdout] | --------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 244 | fn iter(&self) -> $crate::Iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error_chain.rs:300:25 [INFO] [stdout] | [INFO] [stdout] 300 | pub fn iter(&self) -> $crate::Iter { [INFO] [stdout] | ^^^^^ ------------ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] ::: src/lib.rs:823:5 [INFO] [stdout] | [INFO] [stdout] 823 | error_chain! {} [INFO] [stdout] | --------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 300 | pub fn iter(&self) -> $crate::Iter<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:8:5 [INFO] [stdout] | [INFO] [stdout] 8 | / error_chain! { [INFO] [stdout] 9 | | types { [INFO] [stdout] 10 | | Error, ErrorKind, ResultExt, Result; [INFO] [stdout] ... | [INFO] [stdout] 17 | | errors { } [INFO] [stdout] 18 | | }; [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [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 `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:23:5 [INFO] [stdout] | [INFO] [stdout] 23 | / error_chain! { [INFO] [stdout] 24 | | types { } [INFO] [stdout] 25 | | [INFO] [stdout] 26 | | links { } [INFO] [stdout] ... | [INFO] [stdout] 30 | | errors { } [INFO] [stdout] 31 | | }; [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:36:5 [INFO] [stdout] | [INFO] [stdout] 36 | / error_chain! { [INFO] [stdout] 37 | | links { } [INFO] [stdout] 38 | | [INFO] [stdout] 39 | | foreign_links { } [INFO] [stdout] 40 | | [INFO] [stdout] 41 | | errors { } [INFO] [stdout] 42 | | }; [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:47:5 [INFO] [stdout] | [INFO] [stdout] 47 | / error_chain! { [INFO] [stdout] 48 | | links { } [INFO] [stdout] 49 | | [INFO] [stdout] 50 | | foreign_links { } [INFO] [stdout] ... | [INFO] [stdout] 58 | | }; [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:63:5 [INFO] [stdout] | [INFO] [stdout] 63 | / error_chain! { [INFO] [stdout] 64 | | types { } [INFO] [stdout] 65 | | [INFO] [stdout] 66 | | links { } [INFO] [stdout] ... | [INFO] [stdout] 76 | | }; [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:81:5 [INFO] [stdout] | [INFO] [stdout] 81 | / error_chain! { [INFO] [stdout] 82 | | errors { [INFO] [stdout] 83 | | HttpStatus(e: u32) { [INFO] [stdout] 84 | | description("http request returned an unsuccessful status code") [INFO] [stdout] ... | [INFO] [stdout] 88 | | }; [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:93:5 [INFO] [stdout] | [INFO] [stdout] 93 | / error_chain! { [INFO] [stdout] 94 | | types { } [INFO] [stdout] 95 | | [INFO] [stdout] 96 | | foreign_links { } [INFO] [stdout] ... | [INFO] [stdout] 104 | | }; [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:109:5 [INFO] [stdout] | [INFO] [stdout] 109 | / error_chain! { [INFO] [stdout] 110 | | types { } [INFO] [stdout] 111 | | [INFO] [stdout] 112 | | links { } [INFO] [stdout] ... | [INFO] [stdout] 122 | | }; [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:127:5 [INFO] [stdout] | [INFO] [stdout] 127 | error_chain! { types { } links { } foreign_links { } errors { } }; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:132:5 [INFO] [stdout] | [INFO] [stdout] 132 | error_chain! { links { } types { } foreign_links { } errors { } }; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:137:5 [INFO] [stdout] | [INFO] [stdout] 137 | error_chain! { foreign_links { } links { } errors { } types { } }; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:142:5 [INFO] [stdout] | [INFO] [stdout] 142 | error_chain! { errors { } types { } foreign_links { } }; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:147:5 [INFO] [stdout] | [INFO] [stdout] 147 | error_chain! { foreign_links { } types { } }; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:152:5 [INFO] [stdout] | [INFO] [stdout] 152 | / error_chain! { [INFO] [stdout] 153 | | links { } [INFO] [stdout] 154 | | [INFO] [stdout] 155 | | errors { [INFO] [stdout] ... | [INFO] [stdout] 163 | | foreign_links { } [INFO] [stdout] 164 | | }; [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:169:5 [INFO] [stdout] | [INFO] [stdout] 169 | / error_chain! { [INFO] [stdout] 170 | | links { } [INFO] [stdout] 171 | | [INFO] [stdout] 172 | | foreign_links { } [INFO] [stdout] ... | [INFO] [stdout] 177 | | }; [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:182:5 [INFO] [stdout] | [INFO] [stdout] 182 | / error_chain! { [INFO] [stdout] 183 | | links { } [INFO] [stdout] 184 | | [INFO] [stdout] 185 | | foreign_links { } [INFO] [stdout] ... | [INFO] [stdout] 191 | | }; [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:196:5 [INFO] [stdout] | [INFO] [stdout] 196 | error_chain! {}; [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `build` [INFO] [stdout] --> tests/tests.rs:205:30 [INFO] [stdout] | [INFO] [stdout] 205 | let cmd_folder = if cfg!(build = "debug") { [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(build, values("debug"))'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(build, values(\"debug\"))");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `build` [INFO] [stdout] --> tests/tests.rs:207:20 [INFO] [stdout] | [INFO] [stdout] 207 | } else if cfg!(build = "release") { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(build, values("release"))'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(build, values(\"release\"))");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:242:5 [INFO] [stdout] | [INFO] [stdout] 242 | / error_chain! { [INFO] [stdout] 243 | | foreign_links { [INFO] [stdout] 244 | | Fmt(fmt::Error); [INFO] [stdout] ... | [INFO] [stdout] 249 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:259:5 [INFO] [stdout] | [INFO] [stdout] 259 | / error_chain! { [INFO] [stdout] 260 | | errors { [INFO] [stdout] 261 | | Test [INFO] [stdout] 262 | | } [INFO] [stdout] 263 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:278:9 [INFO] [stdout] | [INFO] [stdout] 278 | error_chain! {} [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:281:5 [INFO] [stdout] | [INFO] [stdout] 281 | / error_chain! { [INFO] [stdout] 282 | | links { [INFO] [stdout] 283 | | Test(test::Error, test::ErrorKind); [INFO] [stdout] 284 | | } [INFO] [stdout] 285 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stdout] --> tests/tests.rs:374:15 [INFO] [stdout] | [INFO] [stdout] 374 | #[cfg(not(has_error_source))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stdout] --> tests/tests.rs:384:11 [INFO] [stdout] | [INFO] [stdout] 384 | #[cfg(has_error_source)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stdout] --> tests/tests.rs:305:19 [INFO] [stdout] | [INFO] [stdout] 305 | #[cfg(not(has_error_source))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stdout] --> tests/tests.rs:310:15 [INFO] [stdout] | [INFO] [stdout] 310 | #[cfg(has_error_source)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stdout] --> tests/tests.rs:330:19 [INFO] [stdout] | [INFO] [stdout] 330 | #[cfg(not(has_error_source))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stdout] --> tests/tests.rs:335:15 [INFO] [stdout] | [INFO] [stdout] 335 | #[cfg(has_error_source)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:347:5 [INFO] [stdout] | [INFO] [stdout] 347 | / error_chain! { [INFO] [stdout] 348 | | types{ [INFO] [stdout] 349 | | Error, ErrorKind, ResultExt, Result; [INFO] [stdout] ... | [INFO] [stdout] 356 | | errors {} [INFO] [stdout] 357 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:436:5 [INFO] [stdout] | [INFO] [stdout] 436 | / error_chain! { [INFO] [stdout] 437 | | types { [INFO] [stdout] 438 | | Error, ErrorKind, ResultExt, Result; [INFO] [stdout] ... | [INFO] [stdout] 455 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:460:5 [INFO] [stdout] | [INFO] [stdout] 460 | / error_chain! { [INFO] [stdout] 461 | | types { [INFO] [stdout] 462 | | Error, ErrorKind, ResultExt, Result; [INFO] [stdout] 463 | | } [INFO] [stdout] 464 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:470:5 [INFO] [stdout] | [INFO] [stdout] 470 | / error_chain! { [INFO] [stdout] 471 | | types { [INFO] [stdout] 472 | | Error, ErrorKind, ResultExt; [INFO] [stdout] 473 | | } [INFO] [stdout] 474 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:481:9 [INFO] [stdout] | [INFO] [stdout] 481 | error_chain! {} [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:484:5 [INFO] [stdout] | [INFO] [stdout] 484 | / error_chain! { [INFO] [stdout] 485 | | links { [INFO] [stdout] 486 | | Inner(inner::Error, inner::ErrorKind) #[doc = "Doc"]; [INFO] [stdout] ... | [INFO] [stdout] 495 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:500:5 [INFO] [stdout] | [INFO] [stdout] 500 | / error_chain! { [INFO] [stdout] 501 | | types { [INFO] [stdout] 502 | | MyError, MyErrorKind, MyResultExt, MyResult; [INFO] [stdout] 503 | | } [INFO] [stdout] 504 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:505:5 [INFO] [stdout] | [INFO] [stdout] 505 | error_chain! {} [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:511:5 [INFO] [stdout] | [INFO] [stdout] 511 | error_chain! {} [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:517:5 [INFO] [stdout] | [INFO] [stdout] 517 | / error_chain! { [INFO] [stdout] 518 | | links { [INFO] [stdout] 519 | | Download(error_chain::mock::Error, error_chain::mock::ErrorKind); [INFO] [stdout] ... | [INFO] [stdout] 529 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:534:5 [INFO] [stdout] | [INFO] [stdout] 534 | / error_chain! { [INFO] [stdout] 535 | | links { } [INFO] [stdout] 536 | | [INFO] [stdout] 537 | | foreign_links { } [INFO] [stdout] 538 | | [INFO] [stdout] 539 | | errors { } [INFO] [stdout] 540 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:551:5 [INFO] [stdout] | [INFO] [stdout] 551 | error_chain! {} [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:566:5 [INFO] [stdout] | [INFO] [stdout] 566 | / error_chain! { [INFO] [stdout] 567 | | errors { [INFO] [stdout] 568 | | LocatingWorkingDir { [INFO] [stdout] 569 | | description("could not locate working directory") [INFO] [stdout] ... | [INFO] [stdout] 577 | | foreign_links { } [INFO] [stdout] 578 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:583:5 [INFO] [stdout] | [INFO] [stdout] 583 | / error_chain! { [INFO] [stdout] 584 | | errors { Foo } [INFO] [stdout] 585 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:602:5 [INFO] [stdout] | [INFO] [stdout] 602 | / error_chain! { [INFO] [stdout] 603 | | errors { Bar } [INFO] [stdout] 604 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:619:5 [INFO] [stdout] | [INFO] [stdout] 619 | / error_chain! { [INFO] [stdout] 620 | | types { [INFO] [stdout] 621 | | MyError, MyErrorKind, MyResultExt, MyResult; [INFO] [stdout] 622 | | } [INFO] [stdout] 623 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:639:5 [INFO] [stdout] | [INFO] [stdout] 639 | / error_chain! { [INFO] [stdout] 640 | | foreign_links { [INFO] [stdout] 641 | | VarErr(VarError); [INFO] [stdout] ... | [INFO] [stdout] 647 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:670:5 [INFO] [stdout] | [INFO] [stdout] 670 | / error_chain! { [INFO] [stdout] 671 | | links { } [INFO] [stdout] 672 | | [INFO] [stdout] 673 | | foreign_links { } [INFO] [stdout] ... | [INFO] [stdout] 681 | | }; [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:686:5 [INFO] [stdout] | [INFO] [stdout] 686 | / error_chain! { [INFO] [stdout] 687 | | links { } [INFO] [stdout] 688 | | [INFO] [stdout] 689 | | foreign_links { } [INFO] [stdout] ... | [INFO] [stdout] 697 | | }; [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stdout] --> tests/tests.rs:702:5 [INFO] [stdout] | [INFO] [stdout] 702 | / error_chain! { [INFO] [stdout] 703 | | skip_msg_variant [INFO] [stdout] 704 | | [INFO] [stdout] 705 | | errors { [INFO] [stdout] ... | [INFO] [stdout] 711 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `#[doc(test(...)]` takes a list of attributes [INFO] [stdout] --> tests/tests.rs:508:7 [INFO] [stdout] | [INFO] [stdout] 508 | #[doc(test)] [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(invalid_doc_attributes)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 2.23s [INFO] running `Command { std: "docker" "inspect" "70e739f5497b345f37e733f04aa3b9b7b91502f64e9c246ff7e05d0cc1a9ec29", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "70e739f5497b345f37e733f04aa3b9b7b91502f64e9c246ff7e05d0cc1a9ec29", kill_on_drop: false }` [INFO] [stdout] 70e739f5497b345f37e733f04aa3b9b7b91502f64e9c246ff7e05d0cc1a9ec29 [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=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] c65d067e892fdd1c06b6f01858e2b29f42358aded670a5fc42db8225f21278b0 [INFO] running `Command { std: "docker" "start" "-a" "c65d067e892fdd1c06b6f01858e2b29f42358aded670a5fc42db8225f21278b0", kill_on_drop: false }` [INFO] [stderr] warning: no edition set: defaulting to the 2015 edition while the latest is 2024 [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stderr] --> src/error_chain.rs:3:11 [INFO] [stderr] | [INFO] [stderr] 3 | #[cfg(not(has_error_source))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stderr] --> src/error_chain.rs:36:7 [INFO] [stderr] | [INFO] [stderr] 36 | #[cfg(has_error_source)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> src/error_chain.rs:73:7 [INFO] [stderr] | [INFO] [stderr] 73 | #[cfg(has_error_description_deprecated)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> src/error_chain.rs:82:11 [INFO] [stderr] | [INFO] [stderr] 82 | #[cfg(not(has_error_description_deprecated))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> src/error_chain.rs:323:23 [INFO] [stderr] | [INFO] [stderr] 323 | #[cfg(not(has_error_description_deprecated))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/example_generated.rs:24:5 [INFO] [stderr] | [INFO] [stderr] 24 | error_chain! {} [INFO] [stderr] | --------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> src/error_chain.rs:323:23 [INFO] [stderr] | [INFO] [stderr] 323 | #[cfg(not(has_error_description_deprecated))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/example_generated.rs:27:1 [INFO] [stderr] | [INFO] [stderr] 27 | / error_chain! { [INFO] [stderr] 28 | | links { [INFO] [stderr] 29 | | Inner(inner::Error, inner::ErrorKind) #[doc = "Link to another `ErrorChain`."]; [INFO] [stderr] ... | [INFO] [stderr] 38 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stderr] --> src/lib.rs:581:31 [INFO] [stderr] | [INFO] [stderr] 581 | #[cfg(not(has_error_source))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stderr] --> src/lib.rs:583:27 [INFO] [stderr] | [INFO] [stderr] 583 | #[cfg(has_error_source)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> src/error_chain.rs:323:23 [INFO] [stderr] | [INFO] [stderr] 323 | #[cfg(not(has_error_description_deprecated))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/lib.rs:823:5 [INFO] [stderr] | [INFO] [stderr] 823 | error_chain! {} [INFO] [stderr] | --------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/lib.rs:615:13 [INFO] [stderr] | [INFO] [stderr] 615 | fn iter(&self) -> Iter; [INFO] [stderr] | ^^^^^ ---- the same lifetime is hidden here [INFO] [stderr] | | [INFO] [stderr] | the lifetime is elided here [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 615 | fn iter(&self) -> Iter<'_>; [INFO] [stderr] | ++++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/error_chain.rs:244:21 [INFO] [stderr] | [INFO] [stderr] 244 | fn iter(&self) -> $crate::Iter { [INFO] [stderr] | ^^^^^ ------------ the same lifetime is hidden here [INFO] [stderr] | | [INFO] [stderr] | the lifetime is elided here [INFO] [stderr] | [INFO] [stderr] ::: src/example_generated.rs:27:1 [INFO] [stderr] | [INFO] [stderr] 27 | / error_chain! { [INFO] [stderr] 28 | | links { [INFO] [stderr] 29 | | Inner(inner::Error, inner::ErrorKind) #[doc = "Link to another `ErrorChain`."]; [INFO] [stderr] ... | [INFO] [stderr] 38 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 244 | fn iter(&self) -> $crate::Iter<'_> { [INFO] [stderr] | ++++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/error_chain.rs:300:25 [INFO] [stderr] | [INFO] [stderr] 300 | pub fn iter(&self) -> $crate::Iter { [INFO] [stderr] | ^^^^^ ------------ the same lifetime is hidden here [INFO] [stderr] | | [INFO] [stderr] | the lifetime is elided here [INFO] [stderr] | [INFO] [stderr] ::: src/example_generated.rs:27:1 [INFO] [stderr] | [INFO] [stderr] 27 | / error_chain! { [INFO] [stderr] 28 | | links { [INFO] [stderr] 29 | | Inner(inner::Error, inner::ErrorKind) #[doc = "Link to another `ErrorChain`."]; [INFO] [stderr] ... | [INFO] [stderr] 38 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 300 | pub fn iter(&self) -> $crate::Iter<'_> { [INFO] [stderr] | ++++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/error_chain.rs:244:21 [INFO] [stderr] | [INFO] [stderr] 244 | fn iter(&self) -> $crate::Iter { [INFO] [stderr] | ^^^^^ ------------ the same lifetime is hidden here [INFO] [stderr] | | [INFO] [stderr] | the lifetime is elided here [INFO] [stderr] | [INFO] [stderr] ::: src/example_generated.rs:24:5 [INFO] [stderr] | [INFO] [stderr] 24 | error_chain! {} [INFO] [stderr] | --------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 244 | fn iter(&self) -> $crate::Iter<'_> { [INFO] [stderr] | ++++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/error_chain.rs:300:25 [INFO] [stderr] | [INFO] [stderr] 300 | pub fn iter(&self) -> $crate::Iter { [INFO] [stderr] | ^^^^^ ------------ the same lifetime is hidden here [INFO] [stderr] | | [INFO] [stderr] | the lifetime is elided here [INFO] [stderr] | [INFO] [stderr] ::: src/example_generated.rs:24:5 [INFO] [stderr] | [INFO] [stderr] 24 | error_chain! {} [INFO] [stderr] | --------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 300 | pub fn iter(&self) -> $crate::Iter<'_> { [INFO] [stderr] | ++++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/error_chain.rs:244:21 [INFO] [stderr] | [INFO] [stderr] 244 | fn iter(&self) -> $crate::Iter { [INFO] [stderr] | ^^^^^ ------------ the same lifetime is hidden here [INFO] [stderr] | | [INFO] [stderr] | the lifetime is elided here [INFO] [stderr] | [INFO] [stderr] ::: src/lib.rs:823:5 [INFO] [stderr] | [INFO] [stderr] 823 | error_chain! {} [INFO] [stderr] | --------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 244 | fn iter(&self) -> $crate::Iter<'_> { [INFO] [stderr] | ++++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/error_chain.rs:300:25 [INFO] [stderr] | [INFO] [stderr] 300 | pub fn iter(&self) -> $crate::Iter { [INFO] [stderr] | ^^^^^ ------------ the same lifetime is hidden here [INFO] [stderr] | | [INFO] [stderr] | the lifetime is elided here [INFO] [stderr] | [INFO] [stderr] ::: src/lib.rs:823:5 [INFO] [stderr] | [INFO] [stderr] 823 | error_chain! {} [INFO] [stderr] | --------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 300 | pub fn iter(&self) -> $crate::Iter<'_> { [INFO] [stderr] | ++++ [INFO] [stderr] [INFO] [stderr] warning: `error-chain` (lib) generated 16 warnings [INFO] [stderr] warning: `error-chain` (lib test) generated 16 warnings (16 duplicates) [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> examples/has_backtrace.rs:8:1 [INFO] [stderr] | [INFO] [stderr] 8 | / error_chain! { [INFO] [stderr] 9 | | errors { [INFO] [stderr] 10 | | MyError [INFO] [stderr] 11 | | } [INFO] [stderr] 12 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [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 `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `a_feature` [INFO] [stderr] --> examples/all.rs:8:7 [INFO] [stderr] | [INFO] [stderr] 8 | #[cfg(feature = "a_feature")] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `backtrace`, `default`, and `example_generated` [INFO] [stderr] = help: consider adding `a_feature` as a feature in `Cargo.toml` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `a_feature` [INFO] [stderr] --> examples/all.rs:27:59 [INFO] [stderr] | [INFO] [stderr] 27 | Feature(feature::Error, feature::ErrorKind) #[cfg(feature = "a_feature")]; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `backtrace`, `default`, and `example_generated` [INFO] [stderr] = help: consider adding `a_feature` as a feature in `Cargo.toml` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> examples/all.rs:5:5 [INFO] [stderr] | [INFO] [stderr] 5 | error_chain! {} [INFO] [stderr] | ^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> examples/all.rs:13:1 [INFO] [stderr] | [INFO] [stderr] 13 | / error_chain! { [INFO] [stderr] 14 | | // Types generated by the macro. If empty or absent, it defaults to [INFO] [stderr] 15 | | // Error, ErrorKind, Result; [INFO] [stderr] 16 | | types { [INFO] [stderr] ... | [INFO] [stderr] 34 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> examples/quickstart.rs:17:5 [INFO] [stderr] | [INFO] [stderr] 17 | error_chain! {} [INFO] [stderr] | ^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [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 `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> examples/doc.rs:10:5 [INFO] [stderr] | [INFO] [stderr] 10 | error_chain! {} [INFO] [stderr] | ^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [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 `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> examples/doc.rs:13:1 [INFO] [stderr] | [INFO] [stderr] 13 | / error_chain! { [INFO] [stderr] 14 | | links { [INFO] [stderr] 15 | | Inner(inner::Error, inner::ErrorKind) #[doc = "Doc"]; [INFO] [stderr] ... | [INFO] [stderr] 26 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> examples/chain_err.rs:13:5 [INFO] [stderr] | [INFO] [stderr] 13 | / error_chain! { [INFO] [stderr] 14 | | foreign_links { [INFO] [stderr] 15 | | Io(io::Error) #[doc = "Error during IO"]; [INFO] [stderr] ... | [INFO] [stderr] 29 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [INFO] [stderr] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [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 `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/quick_main.rs:5:1 [INFO] [stderr] | [INFO] [stderr] 5 | error_chain!(); [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [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 `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:8:5 [INFO] [stderr] | [INFO] [stderr] 8 | / error_chain! { [INFO] [stderr] 9 | | types { [INFO] [stderr] 10 | | Error, ErrorKind, ResultExt, Result; [INFO] [stderr] ... | [INFO] [stderr] 17 | | errors { } [INFO] [stderr] 18 | | }; [INFO] [stderr] | |_____^ [INFO] [stderr] | [INFO] [stderr] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [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 `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:23:5 [INFO] [stderr] | [INFO] [stderr] 23 | / error_chain! { [INFO] [stderr] 24 | | types { } [INFO] [stderr] 25 | | [INFO] [stderr] 26 | | links { } [INFO] [stderr] ... | [INFO] [stderr] 30 | | errors { } [INFO] [stderr] 31 | | }; [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:36:5 [INFO] [stderr] | [INFO] [stderr] 36 | / error_chain! { [INFO] [stderr] 37 | | links { } [INFO] [stderr] 38 | | [INFO] [stderr] 39 | | foreign_links { } [INFO] [stderr] 40 | | [INFO] [stderr] 41 | | errors { } [INFO] [stderr] 42 | | }; [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:47:5 [INFO] [stderr] | [INFO] [stderr] 47 | / error_chain! { [INFO] [stderr] 48 | | links { } [INFO] [stderr] 49 | | [INFO] [stderr] 50 | | foreign_links { } [INFO] [stderr] ... | [INFO] [stderr] 58 | | }; [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:63:5 [INFO] [stderr] | [INFO] [stderr] 63 | / error_chain! { [INFO] [stderr] 64 | | types { } [INFO] [stderr] 65 | | [INFO] [stderr] 66 | | links { } [INFO] [stderr] ... | [INFO] [stderr] 76 | | }; [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:81:5 [INFO] [stderr] | [INFO] [stderr] 81 | / error_chain! { [INFO] [stderr] 82 | | errors { [INFO] [stderr] 83 | | HttpStatus(e: u32) { [INFO] [stderr] 84 | | description("http request returned an unsuccessful status code") [INFO] [stderr] ... | [INFO] [stderr] 88 | | }; [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:93:5 [INFO] [stderr] | [INFO] [stderr] 93 | / error_chain! { [INFO] [stderr] 94 | | types { } [INFO] [stderr] 95 | | [INFO] [stderr] 96 | | foreign_links { } [INFO] [stderr] ... | [INFO] [stderr] 104 | | }; [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:109:5 [INFO] [stderr] | [INFO] [stderr] 109 | / error_chain! { [INFO] [stderr] 110 | | types { } [INFO] [stderr] 111 | | [INFO] [stderr] 112 | | links { } [INFO] [stderr] ... | [INFO] [stderr] 122 | | }; [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:127:5 [INFO] [stderr] | [INFO] [stderr] 127 | error_chain! { types { } links { } foreign_links { } errors { } }; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:132:5 [INFO] [stderr] | [INFO] [stderr] 132 | error_chain! { links { } types { } foreign_links { } errors { } }; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:137:5 [INFO] [stderr] | [INFO] [stderr] 137 | error_chain! { foreign_links { } links { } errors { } types { } }; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:142:5 [INFO] [stderr] | [INFO] [stderr] 142 | error_chain! { errors { } types { } foreign_links { } }; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:147:5 [INFO] [stderr] | [INFO] [stderr] 147 | error_chain! { foreign_links { } types { } }; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:152:5 [INFO] [stderr] | [INFO] [stderr] 152 | / error_chain! { [INFO] [stderr] 153 | | links { } [INFO] [stderr] 154 | | [INFO] [stderr] 155 | | errors { [INFO] [stderr] ... | [INFO] [stderr] 163 | | foreign_links { } [INFO] [stderr] 164 | | }; [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:169:5 [INFO] [stderr] | [INFO] [stderr] 169 | / error_chain! { [INFO] [stderr] 170 | | links { } [INFO] [stderr] 171 | | [INFO] [stderr] 172 | | foreign_links { } [INFO] [stderr] ... | [INFO] [stderr] 177 | | }; [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:182:5 [INFO] [stderr] | [INFO] [stderr] 182 | / error_chain! { [INFO] [stderr] 183 | | links { } [INFO] [stderr] 184 | | [INFO] [stderr] 185 | | foreign_links { } [INFO] [stderr] ... | [INFO] [stderr] 191 | | }; [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:196:5 [INFO] [stderr] | [INFO] [stderr] 196 | error_chain! {}; [INFO] [stderr] | ^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `build` [INFO] [stderr] --> tests/tests.rs:205:30 [INFO] [stderr] | [INFO] [stderr] 205 | let cmd_folder = if cfg!(build = "debug") { [INFO] [stderr] | ^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(build, values("debug"))'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(build, values(\"debug\"))");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `build` [INFO] [stderr] --> tests/tests.rs:207:20 [INFO] [stderr] | [INFO] [stderr] 207 | } else if cfg!(build = "release") { [INFO] [stderr] | ^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(build, values("release"))'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(build, values(\"release\"))");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:242:5 [INFO] [stderr] | [INFO] [stderr] 242 | / error_chain! { [INFO] [stderr] 243 | | foreign_links { [INFO] [stderr] 244 | | Fmt(fmt::Error); [INFO] [stderr] ... | [INFO] [stderr] 249 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:259:5 [INFO] [stderr] | [INFO] [stderr] 259 | / error_chain! { [INFO] [stderr] 260 | | errors { [INFO] [stderr] 261 | | Test [INFO] [stderr] 262 | | } [INFO] [stderr] 263 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:278:9 [INFO] [stderr] | [INFO] [stderr] 278 | error_chain! {} [INFO] [stderr] | ^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:281:5 [INFO] [stderr] | [INFO] [stderr] 281 | / error_chain! { [INFO] [stderr] 282 | | links { [INFO] [stderr] 283 | | Test(test::Error, test::ErrorKind); [INFO] [stderr] 284 | | } [INFO] [stderr] 285 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stderr] --> tests/tests.rs:374:15 [INFO] [stderr] | [INFO] [stderr] 374 | #[cfg(not(has_error_source))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stderr] --> tests/tests.rs:384:11 [INFO] [stderr] | [INFO] [stderr] 384 | #[cfg(has_error_source)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stderr] --> tests/tests.rs:305:19 [INFO] [stderr] | [INFO] [stderr] 305 | #[cfg(not(has_error_source))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stderr] --> tests/tests.rs:310:15 [INFO] [stderr] | [INFO] [stderr] 310 | #[cfg(has_error_source)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stderr] --> tests/tests.rs:330:19 [INFO] [stderr] | [INFO] [stderr] 330 | #[cfg(not(has_error_source))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_source` [INFO] [stderr] --> tests/tests.rs:335:15 [INFO] [stderr] | [INFO] [stderr] 335 | #[cfg(has_error_source)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:347:5 [INFO] [stderr] | [INFO] [stderr] 347 | / error_chain! { [INFO] [stderr] 348 | | types{ [INFO] [stderr] 349 | | Error, ErrorKind, ResultExt, Result; [INFO] [stderr] ... | [INFO] [stderr] 356 | | errors {} [INFO] [stderr] 357 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:436:5 [INFO] [stderr] | [INFO] [stderr] 436 | / error_chain! { [INFO] [stderr] 437 | | types { [INFO] [stderr] 438 | | Error, ErrorKind, ResultExt, Result; [INFO] [stderr] ... | [INFO] [stderr] 455 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:460:5 [INFO] [stderr] | [INFO] [stderr] 460 | / error_chain! { [INFO] [stderr] 461 | | types { [INFO] [stderr] 462 | | Error, ErrorKind, ResultExt, Result; [INFO] [stderr] 463 | | } [INFO] [stderr] 464 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:470:5 [INFO] [stderr] | [INFO] [stderr] 470 | / error_chain! { [INFO] [stderr] 471 | | types { [INFO] [stderr] 472 | | Error, ErrorKind, ResultExt; [INFO] [stderr] 473 | | } [INFO] [stderr] 474 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:481:9 [INFO] [stderr] | [INFO] [stderr] 481 | error_chain! {} [INFO] [stderr] | ^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:484:5 [INFO] [stderr] | [INFO] [stderr] 484 | / error_chain! { [INFO] [stderr] 485 | | links { [INFO] [stderr] 486 | | Inner(inner::Error, inner::ErrorKind) #[doc = "Doc"]; [INFO] [stderr] ... | [INFO] [stderr] 495 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:500:5 [INFO] [stderr] | [INFO] [stderr] 500 | / error_chain! { [INFO] [stderr] 501 | | types { [INFO] [stderr] 502 | | MyError, MyErrorKind, MyResultExt, MyResult; [INFO] [stderr] 503 | | } [INFO] [stderr] 504 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:505:5 [INFO] [stderr] | [INFO] [stderr] 505 | error_chain! {} [INFO] [stderr] | ^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:511:5 [INFO] [stderr] | [INFO] [stderr] 511 | error_chain! {} [INFO] [stderr] | ^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:517:5 [INFO] [stderr] | [INFO] [stderr] 517 | / error_chain! { [INFO] [stderr] 518 | | links { [INFO] [stderr] 519 | | Download(error_chain::mock::Error, error_chain::mock::ErrorKind); [INFO] [stderr] ... | [INFO] [stderr] 529 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:534:5 [INFO] [stderr] | [INFO] [stderr] 534 | / error_chain! { [INFO] [stderr] 535 | | links { } [INFO] [stderr] 536 | | [INFO] [stderr] 537 | | foreign_links { } [INFO] [stderr] 538 | | [INFO] [stderr] 539 | | errors { } [INFO] [stderr] 540 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:551:5 [INFO] [stderr] | [INFO] [stderr] 551 | error_chain! {} [INFO] [stderr] | ^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:566:5 [INFO] [stderr] | [INFO] [stderr] 566 | / error_chain! { [INFO] [stderr] 567 | | errors { [INFO] [stderr] 568 | | LocatingWorkingDir { [INFO] [stderr] 569 | | description("could not locate working directory") [INFO] [stderr] ... | [INFO] [stderr] 577 | | foreign_links { } [INFO] [stderr] 578 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:583:5 [INFO] [stderr] | [INFO] [stderr] 583 | / error_chain! { [INFO] [stderr] 584 | | errors { Foo } [INFO] [stderr] 585 | | } [INFO] [stdout] [INFO] [stderr] | |_____^ [INFO] [stdout] running 0 tests [INFO] [stderr] | [INFO] [stdout] [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] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stderr] = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stdout] [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:602:5 [INFO] [stderr] | [INFO] [stderr] 602 | / error_chain! { [INFO] [stderr] 603 | | errors { Bar } [INFO] [stderr] 604 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:619:5 [INFO] [stderr] | [INFO] [stderr] 619 | / error_chain! { [INFO] [stderr] 620 | | types { [INFO] [stderr] 621 | | MyError, MyErrorKind, MyResultExt, MyResult; [INFO] [stderr] 622 | | } [INFO] [stderr] 623 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:639:5 [INFO] [stderr] | [INFO] [stderr] 639 | / error_chain! { [INFO] [stderr] 640 | | foreign_links { [INFO] [stderr] 641 | | VarErr(VarError); [INFO] [stderr] ... | [INFO] [stderr] 647 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:670:5 [INFO] [stderr] | [INFO] [stderr] 670 | / error_chain! { [INFO] [stderr] 671 | | links { } [INFO] [stderr] 672 | | [INFO] [stderr] 673 | | foreign_links { } [INFO] [stderr] ... | [INFO] [stderr] 681 | | }; [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:686:5 [INFO] [stderr] | [INFO] [stderr] 686 | / error_chain! { [INFO] [stderr] 687 | | links { } [INFO] [stderr] 688 | | [INFO] [stderr] 689 | | foreign_links { } [INFO] [stderr] ... | [INFO] [stderr] 697 | | }; [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> tests/tests.rs:702:5 [INFO] [stderr] | [INFO] [stderr] 702 | / error_chain! { [INFO] [stderr] 703 | | skip_msg_variant [INFO] [stderr] 704 | | [INFO] [stderr] 705 | | errors { [INFO] [stderr] ... | [INFO] [stderr] 711 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: `#[doc(test(...)]` takes a list of attributes [INFO] [stderr] --> tests/tests.rs:508:7 [INFO] [stdout] [INFO] [stderr] | [INFO] [stdout] running 0 tests [INFO] [stderr] 508 | #[doc(test)] [INFO] [stdout] [INFO] [stderr] | ^^^^ [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stderr] | [INFO] [stdout] [INFO] [stderr] = note: `#[warn(invalid_doc_attributes)]` on by default [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `has_error_description_deprecated` [INFO] [stderr] --> examples/size.rs:6:1 [INFO] [stderr] | [INFO] [stderr] 6 | / error_chain! { [INFO] [stderr] 7 | | errors { [INFO] [stderr] 8 | | AVariant [INFO] [stderr] 9 | | Another [INFO] [stderr] 10 | | } [INFO] [stderr] 11 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [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 `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `impl_error_chain_processed` may come from an old version of the `error_chain` crate, try updating your dependency with `cargo update -p error_chain` [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 `impl_error_chain_processed` which comes from the expansion of the macro `error_chain` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: `error-chain` (example "has_backtrace") generated 1 warning [INFO] [stderr] warning: `error-chain` (example "all") generated 4 warnings [INFO] [stderr] warning: `error-chain` (example "quickstart") generated 1 warning [INFO] [stderr] warning: `error-chain` (example "doc") generated 2 warnings [INFO] [stderr] warning: `error-chain` (example "chain_err") generated 1 warning [INFO] [stderr] warning: `error-chain` (test "quick_main") generated 1 warning [INFO] [stderr] warning: `error-chain` (test "tests") generated 50 warnings [INFO] [stderr] warning: `error-chain` (example "size") generated 1 warning [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 0.07s [INFO] [stderr] Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/error_chain-980f5cdf414a941c) [INFO] [stderr] Running tests/quick_main.rs (/opt/rustwide/target/debug/deps/quick_main-748f71d5043b96da) [INFO] [stderr] Running tests/tests.rs (/opt/rustwide/target/debug/deps/tests-4645f6e4e47d4dec) [INFO] [stdout] [INFO] [stdout] running 38 tests [INFO] [stdout] test error_first ... ok [INFO] [stdout] test documentation ... ok [INFO] [stdout] test foreign_link_test::display_underlying_error ... ok [INFO] [stdout] test comma_in_errors_impl ... ok [INFO] [stdout] test links ... ok [INFO] [stdout] test order_test_1 ... ok [INFO] [stdout] test order_test_2 ... ok [INFO] [stdout] test order_test_3 ... ok [INFO] [stdout] test order_test_4 ... ok [INFO] [stdout] test bail ... ok [INFO] [stdout] test empty ... ok [INFO] [stdout] test order_test_5 ... ok [INFO] [stdout] test order_test_6 ... ok [INFO] [stdout] test order_test_7 ... ok [INFO] [stdout] test order_test_8 ... ok [INFO] [stdout] test result_match ... ok [INFO] [stdout] test rustup_regression ... ok [INFO] [stdout] test smoke_test_6 ... ok [INFO] [stdout] test smoke_test_1 ... ok [INFO] [stdout] test smoke_test_2 ... ok [INFO] [stdout] test smoke_test_3 ... ok [INFO] [stdout] test smoke_test_4 ... ok [INFO] [stdout] test smoke_test_5 ... ok [INFO] [stdout] test smoke_test_7 ... ok [INFO] [stdout] test smoke_test_8 ... ok [INFO] [stdout] test trailing_comma_in_errors_impl ... ok [INFO] [stdout] test without_result ... ok [INFO] [stdout] test with_result ... ok [INFO] [stdout] test ensure ... ok [INFO] [stdout] test error_chain_err ... ok [INFO] [stdout] test error_patterns ... ok [INFO] [stdout] test chain_err ... ok [INFO] [stdout] test foreign_link_test::finds_source ... ok [INFO] [stdout] test types_declarations ... ok [INFO] [stdout] test rewrapping ... ok [INFO] [stdout] test skipping_msg_variant ... ok [INFO] [stdout] test has_backtrace_depending_on_env ... FAILED [INFO] [stdout] test foreign_link_test::iterates ... ok [INFO] [stdout] [INFO] [stdout] failures: [INFO] [stdout] [INFO] [stdout] ---- has_backtrace_depending_on_env stdout ---- [INFO] [stdout] [INFO] [stdout] thread 'has_backtrace_depending_on_env' panicked at tests/tests.rs:225:29: [INFO] [stdout] called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" } [INFO] [stdout] stack backtrace: [INFO] [stdout] 0: 0x5ccfde057fe2 - std::backtrace_rs::backtrace::libunwind::trace::h2d45396358f41939 [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/../../backtrace/src/backtrace/libunwind.rs:117:9 [INFO] [stdout] 1: 0x5ccfde057fe2 - std::backtrace_rs::backtrace::trace_unsynchronized::hffcefc0b67f1d6e2 [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/../../backtrace/src/backtrace/mod.rs:66:14 [INFO] [stdout] 2: 0x5ccfde057fe2 - std::sys::backtrace::_print_fmt::hd72f71d23b436b92 [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/sys/backtrace.rs:66:9 [INFO] [stdout] 3: 0x5ccfde057fe2 - ::fmt::hdcfcb6d4c8489523 [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/sys/backtrace.rs:39:26 [INFO] [stdout] 4: 0x5ccfde07dbf3 - core::fmt::rt::Argument::fmt::h2c56b3114963061a [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/core/src/fmt/rt.rs:173:76 [INFO] [stdout] 5: 0x5ccfde07dbf3 - core::fmt::write::h8a494366950f23bb [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/core/src/fmt/mod.rs:1468:25 [INFO] [stdout] 6: 0x5ccfde054e53 - std::io::default_write_fmt::h7b8824096454f323 [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/io/mod.rs:639:11 [INFO] [stdout] 7: 0x5ccfde054e53 - std::io::Write::write_fmt::h4e71294925c334d0 [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/io/mod.rs:1954:13 [INFO] [stdout] 8: 0x5ccfde057e32 - std::sys::backtrace::BacktraceLock::print::hb2a626a81e06b2dc [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/sys/backtrace.rs:42:9 [INFO] [stdout] 9: 0x5ccfde059b39 - std::panicking::default_hook::{{closure}}::h4f78485264f12d10 [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/panicking.rs:300:27 [INFO] [stdout] 10: 0x5ccfde05996e - std::panicking::default_hook::h2c66fc99e962531d [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/panicking.rs:324:9 [INFO] [stdout] 11: 0x5ccfddfa6e54 - as core::ops::function::Fn>::call::hb6bd65493727d71a [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/alloc/src/boxed.rs:1985:9 [INFO] [stdout] 12: 0x5ccfddfa6e54 - test::test_main_with_exit_callback::{{closure}}::h60217ec76a0ece4a [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/test/src/lib.rs:145:21 [INFO] [stdout] 13: 0x5ccfde05a60e - as core::ops::function::Fn>::call::h318e4efb8c1a5689 [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/alloc/src/boxed.rs:1985:9 [INFO] [stdout] 14: 0x5ccfde05a60e - std::panicking::rust_panic_with_hook::h33ac55f64bbd807d [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/panicking.rs:841:13 [INFO] [stdout] 15: 0x5ccfde05a2da - std::panicking::begin_panic_handler::{{closure}}::h30e7cb89678a57fe [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/panicking.rs:706:13 [INFO] [stdout] 16: 0x5ccfde0584e9 - std::sys::backtrace::__rust_end_short_backtrace::hed60f27456c16ced [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/sys/backtrace.rs:174:18 [INFO] [stdout] 17: 0x5ccfde059f6d - __rustc[de2ca18b4c54d5b8]::rust_begin_unwind [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/panicking.rs:697:5 [INFO] [stdout] 18: 0x5ccfde07c5c0 - core::panicking::panic_fmt::h62f63d096dd276af [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/core/src/panicking.rs:75:14 [INFO] [stdout] 19: 0x5ccfde07ca76 - core::result::unwrap_failed::h95bc3f5a607b2c95 [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/core/src/result.rs:1765:5 [INFO] [stdout] 20: 0x5ccfddf6861e - core::result::Result::unwrap::hc27b333f8d0955ad [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/core/src/result.rs:1167:23 [INFO] [stdout] 21: 0x5ccfddf6861e - tests::has_backtrace_depending_on_env::h95113600c60a5df6 [INFO] [stdout] at /opt/rustwide/workdir/tests/tests.rs:225:29 [INFO] [stdout] 22: 0x5ccfddf68427 - tests::has_backtrace_depending_on_env::{{closure}}::h53cb174400e33326 [INFO] [stdout] at /opt/rustwide/workdir/tests/tests.rs:201:36 [INFO] [stdout] 23: 0x5ccfddf62ee6 - core::ops::function::FnOnce::call_once::h389fe87537fc9767 [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/core/src/ops/function.rs:253:5 [INFO] [stdout] 24: 0x5ccfddfac6bb - core::ops::function::FnOnce::call_once::h1f9474f1347fff52 [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/core/src/ops/function.rs:253:5 [INFO] [stdout] 25: 0x5ccfddfac6bb - test::__rust_begin_short_backtrace::ha52ab26e77157f03 [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/test/src/lib.rs:648:18 [INFO] [stdout] 26: 0x5ccfddfab7f5 - test::run_test_in_process::{{closure}}::h229c1a11a50b261f [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/test/src/lib.rs:671:74 [INFO] [stdout] 27: 0x5ccfddfab7f5 - as core::ops::function::FnOnce<()>>::call_once::h78821afbf97b39a9 [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/core/src/panic/unwind_safe.rs:272:9 [INFO] [stdout] 28: 0x5ccfddfab7f5 - std::panicking::catch_unwind::do_call::h53abf3ed5bd32ba3 [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/panicking.rs:589:40 [INFO] [stdout] 29: 0x5ccfddfab7f5 - std::panicking::catch_unwind::h6deb5fe1e91873c9 [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/panicking.rs:552:19 [INFO] [stdout] 30: 0x5ccfddfab7f5 - std::panic::catch_unwind::hea0829b6b565654b [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/panic.rs:359:14 [INFO] [stdout] 31: 0x5ccfddfab7f5 - test::run_test_in_process::hdc44dfecea3db21b [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/test/src/lib.rs:671:27 [INFO] [stdout] 32: 0x5ccfddfab7f5 - test::run_test::{{closure}}::h0364ba59bf23f652 [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/test/src/lib.rs:592:43 [INFO] [stdout] 33: 0x5ccfddf6f3f4 - test::run_test::{{closure}}::h32730b304eec05da [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/test/src/lib.rs:622:41 [INFO] [stdout] 34: 0x5ccfddf6f3f4 - std::sys::backtrace::__rust_begin_short_backtrace::h177cb952fc54ad2c [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/sys/backtrace.rs:158:18 [INFO] [stdout] 35: 0x5ccfddf72dca - std::thread::Builder::spawn_unchecked_::{{closure}}::{{closure}}::h119d903520007597 [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/thread/mod.rs:559:17 [INFO] [stdout] 36: 0x5ccfddf72dca - as core::ops::function::FnOnce<()>>::call_once::hab88401d606702a6 [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/core/src/panic/unwind_safe.rs:272:9 [INFO] [stdout] 37: 0x5ccfddf72dca - std::panicking::catch_unwind::do_call::h163fe12cca9901c2 [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/panicking.rs:589:40 [INFO] [stdout] 38: 0x5ccfddf72dca - std::panicking::catch_unwind::he81557d0e17cc1bc [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/panicking.rs:552:19 [INFO] [stdout] 39: 0x5ccfddf72dca - std::panic::catch_unwind::hc2b8e79c20593955 [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/panic.rs:359:14 [INFO] [stdout] 40: 0x5ccfddf72dca - std::thread::Builder::spawn_unchecked_::{{closure}}::hfa6b4978e07815cc [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/thread/mod.rs:557:30 [INFO] [stdout] 41: 0x5ccfddf72dca - core::ops::function::FnOnce::call_once{{vtable.shim}}::hddcd7484a13fd793 [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/core/src/ops/function.rs:253:5 [INFO] [stdout] 42: 0x5ccfde05d61f - as core::ops::function::FnOnce>::call_once::h5924238c754de3b8 [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/alloc/src/boxed.rs:1971:9 [INFO] [stdout] 43: 0x5ccfde05d61f - std::sys::pal::unix::thread::Thread::new::thread_start::hb6e99e73da4d28f8 [INFO] [stdout] at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/sys/pal/unix/thread.rs:107:17 [INFO] [stdout] 44: 0x7738fc8acaa4 - [INFO] [stdout] 45: 0x7738fc939a34 - clone [INFO] [stdout] 46: 0x0 - [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] failures: [INFO] [stdout] has_backtrace_depending_on_env [INFO] [stdout] [INFO] [stdout] test result: FAILED. 37 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.53s [INFO] [stdout] [INFO] [stderr] error: test failed, to rerun pass `--test tests` [INFO] running `Command { std: "docker" "inspect" "c65d067e892fdd1c06b6f01858e2b29f42358aded670a5fc42db8225f21278b0", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "c65d067e892fdd1c06b6f01858e2b29f42358aded670a5fc42db8225f21278b0", kill_on_drop: false }` [INFO] [stdout] c65d067e892fdd1c06b6f01858e2b29f42358aded670a5fc42db8225f21278b0