D: [iurt_root_command] chroot Building target platforms: noarch Building for target noarch Installing /home/pterjan/rpmbuild/SRPMS/rust-error-chain-0.12.4-0.2.mga10.src.rpm Executing(%mkbuilddir): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.nrXV1o Executing(%prep): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.kTWT2x + umask 022 + cd /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + cd /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build + rm -rf error-chain-0.12.4 + /usr/lib/rpm/rpmuncompress -x /home/pterjan/rpmbuild/SOURCES/error-chain-0.12.4.crate + STATUS=0 + '[' 0 -ne 0 ']' + cd error-chain-0.12.4 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + set -euo pipefail + /usr/bin/mkdir -p target/rpm + /usr/bin/ln -s rpm target/release + /usr/bin/rm -rf .cargo/ + /usr/bin/mkdir -p .cargo + cat + cat + /usr/bin/rm -f Cargo.lock + /usr/bin/rm -f Cargo.toml.orig + RPM_EC=0 ++ jobs -p + exit 0 Executing(%generate_buildrequires): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.jsDfhD + umask 022 + cd /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build + cd error-chain-0.12.4 + /usr/bin/cargo2rpm --path Cargo.toml buildrequires --with-check + RPM_EC=0 ++ jobs -p + exit 0 Executing(%build): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.DStV9r + umask 022 + cd /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build + CFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CFLAGS + CXXFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CXXFLAGS + FFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FFLAGS + FCFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--build-id=sha1 -Wl,--enable-new-dtags -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd error-chain-0.12.4 + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + /usr/bin/env CARGO_HOME=.cargo RUSTC_BOOTSTRAP=1 'RUSTFLAGS=-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn' /usr/bin/cargo build -j16 -Z avoid-dev-deps --profile rpm warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Compiling libc v0.2.180 Compiling object v0.37.3 Compiling memchr v2.7.6 Compiling version_check v0.9.5 Compiling gimli v0.32.3 Compiling adler2 v2.0.1 Compiling cfg-if v1.0.4 Compiling rustc-demangle v0.1.24 Running `/usr/bin/rustc --crate-name build_script_build --edition=2021 /usr/share/cargo/registry/libc-0.2.180/build.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no '--allow=clippy::used_underscore_binding' --allow=unused_qualifications '--warn=clippy::unnecessary_semicolon' '--allow=clippy::unnecessary_cast' '--allow=clippy::uninlined_format_args' '--warn=clippy::ptr_as_ptr' '--allow=clippy::non_minimal_cfg' '--allow=clippy::missing_safety_doc' '--warn=clippy::map_unwrap_or' '--warn=clippy::manual_assert' '--allow=clippy::identity_op' '--warn=clippy::explicit_iter_loop' '--allow=clippy::expl_impl_clone_on_copy' -C debug-assertions=off --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("align", "const-extern-fn", "default", "extra_traits", "rustc-dep-of-std", "rustc-std-workspace-core", "std", "use_std"))' -C metadata=92411a416ecbc327 -C extra-filename=-d139e536c4388098 --out-dir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/build/libc-d139e536c4388098 -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn` Running `/usr/bin/rustc --crate-name build_script_build --edition=2018 /usr/share/cargo/registry/object-0.37.3/build.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no '--allow=clippy::uninlined_format_args' '--allow=clippy::type_complexity' '--allow=clippy::single_match' '--allow=clippy::should_implement_trait' '--allow=clippy::result_unit_err' '--allow=clippy::needless_lifetimes' '--allow=clippy::match_like_matches_macro' '--allow=clippy::manual_flatten' '--allow=clippy::field_reassign_with_default' '--allow=clippy::comparison_chain' '--allow=clippy::collapsible_match' '--allow=clippy::collapsible_if' '--allow=clippy::collapsible_else_if' -C debug-assertions=off --cfg 'feature="archive"' --cfg 'feature="coff"' --cfg 'feature="elf"' --cfg 'feature="macho"' --cfg 'feature="pe"' --cfg 'feature="read_core"' --cfg 'feature="unaligned"' --cfg 'feature="xcoff"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("all", "alloc", "archive", "build", "build_core", "cargo-all", "coff", "compression", "core", "default", "doc", "elf", "macho", "pe", "read", "read_core", "rustc-dep-of-std", "std", "unaligned", "unstable", "unstable-all", "write", "write_core", "write_std", "xcoff"))' -C metadata=cf5cfa5fe8d47825 -C extra-filename=-5cb6537d4d91dbd4 --out-dir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/build/object-5cb6537d4d91dbd4 -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn` Running `/usr/bin/rustc --crate-name version_check --edition=2015 /usr/share/cargo/registry/version_check-0.9.5/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debug-assertions=off --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values())' -C metadata=b0547059fbd0fdc5 -C extra-filename=-2f5fba78a5d5b6fd --out-dir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn` Running `/usr/bin/rustc --crate-name memchr --edition=2021 /usr/share/cargo/registry/memchr-2.7.6/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("alloc", "core", "default", "libc", "logging", "rustc-dep-of-std", "std", "use_std"))' -C metadata=73be854e01212747 -C extra-filename=-cc40006565eabb9a --out-dir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn` Running `/usr/bin/rustc --crate-name gimli --edition=2018 /usr/share/cargo/registry/gimli-0.32.3/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --cfg 'feature="read"' --cfg 'feature="read-core"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "endian-reader", "fallible-iterator", "read", "read-all", "read-core", "std", "write"))' -C metadata=9ee7cbe622d2ffa1 -C extra-filename=-9063cbabff1973c5 --out-dir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn` Running `/usr/bin/rustc --crate-name adler2 --edition=2021 /usr/share/cargo/registry/adler2-2.0.1/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "std"))' -C metadata=ebff469818a58e6b -C extra-filename=-f593994f2f2394b8 --out-dir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn` Running `/usr/bin/rustc --crate-name cfg_if --edition=2018 /usr/share/cargo/registry/cfg-if-1.0.4/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("core", "rustc-dep-of-std"))' -C metadata=08b529e5e0e8f31d -C extra-filename=-882b1cd97dcfd39c --out-dir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn` Running `/usr/bin/rustc --crate-name rustc_demangle --edition=2015 /usr/share/cargo/registry/rustc-demangle-0.1.24/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("compiler_builtins", "core", "rustc-dep-of-std", "std"))' -C metadata=f732bd17317a03e8 -C extra-filename=-68e3e675726e2def --out-dir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn` Compiling miniz_oxide v0.8.9 Running `/usr/bin/rustc --crate-name miniz_oxide --edition=2021 /usr/share/cargo/registry/miniz_oxide-0.8.9/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --warn=unexpected_cfgs --check-cfg 'cfg(fuzzing)' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("alloc", "block-boundary", "core", "default", "rustc-dep-of-std", "serde", "simd", "simd-adler32", "std", "with-alloc"))' -C metadata=2d96ad15da898995 -C extra-filename=-807b6d9be2fa8a8c --out-dir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --extern adler2=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/libadler2-f593994f2f2394b8.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn` Running `/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/build/object-5cb6537d4d91dbd4/build-script-build` Running `/usr/bin/rustc --crate-name object --edition=2018 /usr/share/cargo/registry/object-0.37.3/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 '--allow=clippy::uninlined_format_args' '--allow=clippy::type_complexity' '--allow=clippy::single_match' '--allow=clippy::should_implement_trait' '--allow=clippy::result_unit_err' '--allow=clippy::needless_lifetimes' '--allow=clippy::match_like_matches_macro' '--allow=clippy::manual_flatten' '--allow=clippy::field_reassign_with_default' '--allow=clippy::comparison_chain' '--allow=clippy::collapsible_match' '--allow=clippy::collapsible_if' '--allow=clippy::collapsible_else_if' --cfg 'feature="archive"' --cfg 'feature="coff"' --cfg 'feature="elf"' --cfg 'feature="macho"' --cfg 'feature="pe"' --cfg 'feature="read_core"' --cfg 'feature="unaligned"' --cfg 'feature="xcoff"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("all", "alloc", "archive", "build", "build_core", "cargo-all", "coff", "compression", "core", "default", "doc", "elf", "macho", "pe", "read", "read_core", "rustc-dep-of-std", "std", "unaligned", "unstable", "unstable-all", "write", "write_core", "write_std", "xcoff"))' -C metadata=22a855e38391db5e -C extra-filename=-401faabb8dfffbd2 --out-dir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --extern memchr=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/libmemchr-cc40006565eabb9a.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn --cfg core_error --check-cfg 'cfg(core_error)'` Running `/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/build/libc-d139e536c4388098/build-script-build` Running `/usr/bin/rustc --crate-name libc --edition=2021 /usr/share/cargo/registry/libc-0.2.180/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 '--allow=clippy::used_underscore_binding' --allow=unused_qualifications '--warn=clippy::unnecessary_semicolon' '--allow=clippy::unnecessary_cast' '--allow=clippy::uninlined_format_args' '--warn=clippy::ptr_as_ptr' '--allow=clippy::non_minimal_cfg' '--allow=clippy::missing_safety_doc' '--warn=clippy::map_unwrap_or' '--warn=clippy::manual_assert' '--allow=clippy::identity_op' '--warn=clippy::explicit_iter_loop' '--allow=clippy::expl_impl_clone_on_copy' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("align", "const-extern-fn", "default", "extra_traits", "rustc-dep-of-std", "rustc-std-workspace-core", "std", "use_std"))' -C metadata=5429833b3143d375 -C extra-filename=-99d0b11ae01f7d56 --out-dir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn --cfg freebsd12 --check-cfg 'cfg(emscripten_old_stat_abi)' --check-cfg 'cfg(espidf_time32)' --check-cfg 'cfg(freebsd10)' --check-cfg 'cfg(freebsd11)' --check-cfg 'cfg(freebsd12)' --check-cfg 'cfg(freebsd13)' --check-cfg 'cfg(freebsd14)' --check-cfg 'cfg(freebsd15)' --check-cfg 'cfg(gnu_file_offset_bits64)' --check-cfg 'cfg(gnu_time_bits64)' --check-cfg 'cfg(libc_deny_warnings)' --check-cfg 'cfg(linux_time_bits64)' --check-cfg 'cfg(musl_v1_2_3)' --check-cfg 'cfg(musl32_time64)' --check-cfg 'cfg(vxworks_lt_25_09)' --check-cfg 'cfg(target_os,values("switch","aix","ohos","hurd","rtems","visionos","nuttx","cygwin","qurt"))' --check-cfg 'cfg(target_env,values("illumos","wasi","aix","ohos","nto71_iosock","nto80"))' --check-cfg 'cfg(target_arch,values("loongarch64","mips32r6","mips64r6","csky"))'` Compiling error-chain v0.12.4 (/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4) Running `/usr/bin/rustc --crate-name build_script_build --edition=2015 build.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="backtrace"' --cfg 'feature="default"' --cfg 'feature="example_generated"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("backtrace", "default", "example_generated"))' -C metadata=dd513386a26134d2 -C extra-filename=-21ba31a6c1e41887 --out-dir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/build/error-chain-21ba31a6c1e41887 -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --extern version_check=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/libversion_check-2f5fba78a5d5b6fd.rlib -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn` Running `/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/build/error-chain-21ba31a6c1e41887/build-script-build` Compiling addr2line v0.25.1 Running `/usr/bin/rustc --crate-name addr2line --edition=2018 /usr/share/cargo/registry/addr2line-0.25.1/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("all", "alloc", "bin", "cargo-all", "core", "cpp_demangle", "default", "fallible-iterator", "loader", "rustc-demangle", "rustc-dep-of-std", "smallvec", "std", "wasm"))' -C metadata=3fd56912f17d2d4e -C extra-filename=-71e037598ca7ef41 --out-dir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --extern gimli=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/libgimli-9063cbabff1973c5.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn` Compiling backtrace v0.3.76 Running `/usr/bin/rustc --crate-name backtrace --edition=2021 /usr/share/cargo/registry/backtrace-0.3.76/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --allow=unexpected_cfgs --cfg 'feature="default"' --cfg 'feature="std"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("coresymbolication", "cpp_demangle", "dbghelp", "default", "dl_iterate_phdr", "dladdr", "kernel32", "libunwind", "ruzstd", "serde", "serialize-serde", "std", "unix-backtrace"))' -C metadata=337ae5ba67edaad3 -C extra-filename=-43a9dacd75640d3f --out-dir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --extern addr2line=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/libaddr2line-71e037598ca7ef41.rmeta --extern cfg_if=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/libcfg_if-882b1cd97dcfd39c.rmeta --extern libc=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/liblibc-99d0b11ae01f7d56.rmeta --extern miniz_oxide=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/libminiz_oxide-807b6d9be2fa8a8c.rmeta --extern object=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/libobject-401faabb8dfffbd2.rmeta --extern rustc_demangle=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/librustc_demangle-68e3e675726e2def.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn` Running `/usr/bin/rustc --crate-name error_chain --edition=2015 src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --cfg 'feature="backtrace"' --cfg 'feature="default"' --cfg 'feature="example_generated"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("backtrace", "default", "example_generated"))' -C metadata=4f89d5f7c911219d -C extra-filename=-818d6de54d5481db --out-dir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --extern backtrace=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/libbacktrace-43a9dacd75640d3f.rmeta -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn --cfg has_error_source --cfg has_error_description_deprecated --cfg 'build="release"'` warning: unexpected `cfg` condition name: `has_error_source` --> src/error_chain.rs:3:11 | 3 | #[cfg(not(has_error_source))] | ^^^^^^^^^^^^^^^^ | = help: expected names are: `docsrs`, `feature`, and `test` and 31 more = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` = note: see for more information about checking conditional configuration = note: `#[warn(unexpected_cfgs)]` on by default warning: unexpected `cfg` condition name: `has_error_source` --> src/error_chain.rs:36:7 | 36 | #[cfg(has_error_source)] | ^^^^^^^^^^^^^^^^ | = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> src/error_chain.rs:73:7 | 73 | #[cfg(has_error_description_deprecated)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> src/error_chain.rs:82:11 | 82 | #[cfg(not(has_error_description_deprecated))] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> src/error_chain.rs:323:23 | 323 | #[cfg(not(has_error_description_deprecated))] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ::: src/example_generated.rs:24:5 | 24 | error_chain! {} | --------------- in this macro invocation | = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> src/error_chain.rs:323:23 | 323 | #[cfg(not(has_error_description_deprecated))] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ::: src/example_generated.rs:27:1 | 27 | / error_chain! { 28 | | links { 29 | | Inner(inner::Error, inner::ErrorKind) #[doc = "Link to another `ErrorChain`."]; ... | 38 | | } | |_- in this macro invocation | = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_source` --> src/lib.rs:581:31 | 581 | #[cfg(not(has_error_source))] | ^^^^^^^^^^^^^^^^ | = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition name: `has_error_source` --> src/lib.rs:583:27 | 583 | #[cfg(has_error_source)] | ^^^^^^^^^^^^^^^^ | = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> src/error_chain.rs:323:23 | 323 | #[cfg(not(has_error_description_deprecated))] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ::: src/lib.rs:823:5 | 823 | error_chain! {} | --------------- in this macro invocation | = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` = note: see for more information about checking conditional configuration = 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) warning: hiding a lifetime that's elided elsewhere is confusing --> src/lib.rs:615:13 | 615 | fn iter(&self) -> Iter; | ^^^^^ ^^^^ the same lifetime is hidden here | | | the lifetime is elided here | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default help: use `'_` for type paths | 615 | fn iter(&self) -> Iter<'_>; | ++++ warning: hiding a lifetime that's elided elsewhere is confusing --> src/error_chain.rs:244:21 | 244 | fn iter(&self) -> $crate::Iter { | ^^^^^ ^^^^^^^^^^^^ the same lifetime is hidden here | | | the lifetime is elided here | ::: src/example_generated.rs:27:1 | 27 | / error_chain! { 28 | | links { 29 | | Inner(inner::Error, inner::ErrorKind) #[doc = "Link to another `ErrorChain`."]; ... | 38 | | } | |_- in this macro invocation | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing = 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) help: use `'_` for type paths | 244 | fn iter(&self) -> $crate::Iter<'_> { | ++++ warning: hiding a lifetime that's elided elsewhere is confusing --> src/error_chain.rs:300:25 | 300 | pub fn iter(&self) -> $crate::Iter { | ^^^^^ ^^^^^^^^^^^^ the same lifetime is hidden here | | | the lifetime is elided here | ::: src/example_generated.rs:27:1 | 27 | / error_chain! { 28 | | links { 29 | | Inner(inner::Error, inner::ErrorKind) #[doc = "Link to another `ErrorChain`."]; ... | 38 | | } | |_- in this macro invocation | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing = 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) help: use `'_` for type paths | 300 | pub fn iter(&self) -> $crate::Iter<'_> { | ++++ warning: hiding a lifetime that's elided elsewhere is confusing --> src/error_chain.rs:244:21 | 244 | fn iter(&self) -> $crate::Iter { | ^^^^^ ^^^^^^^^^^^^ the same lifetime is hidden here | | | the lifetime is elided here | ::: src/example_generated.rs:24:5 | 24 | error_chain! {} | --------------- in this macro invocation | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing = 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) help: use `'_` for type paths | 244 | fn iter(&self) -> $crate::Iter<'_> { | ++++ warning: hiding a lifetime that's elided elsewhere is confusing --> src/error_chain.rs:300:25 | 300 | pub fn iter(&self) -> $crate::Iter { | ^^^^^ ^^^^^^^^^^^^ the same lifetime is hidden here | | | the lifetime is elided here | ::: src/example_generated.rs:24:5 | 24 | error_chain! {} | --------------- in this macro invocation | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing = 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) help: use `'_` for type paths | 300 | pub fn iter(&self) -> $crate::Iter<'_> { | ++++ warning: hiding a lifetime that's elided elsewhere is confusing --> src/error_chain.rs:244:21 | 244 | fn iter(&self) -> $crate::Iter { | ^^^^^ ^^^^^^^^^^^^ the same lifetime is hidden here | | | the lifetime is elided here | ::: src/lib.rs:823:5 | 823 | error_chain! {} | --------------- in this macro invocation | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing = 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) help: use `'_` for type paths | 244 | fn iter(&self) -> $crate::Iter<'_> { | ++++ warning: hiding a lifetime that's elided elsewhere is confusing --> src/error_chain.rs:300:25 | 300 | pub fn iter(&self) -> $crate::Iter { | ^^^^^ ^^^^^^^^^^^^ the same lifetime is hidden here | | | the lifetime is elided here | ::: src/lib.rs:823:5 | 823 | error_chain! {} | --------------- in this macro invocation | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing = 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) help: use `'_` for type paths | 300 | pub fn iter(&self) -> $crate::Iter<'_> { | ++++ warning: `error-chain` (lib) generated 16 warnings (run `cargo fix --lib -p error-chain` to apply 7 suggestions) Finished `rpm` profile [optimized + debuginfo] target(s) in 12.51s + RPM_EC=0 ++ jobs -p + exit 0 Executing(%install): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.hU4gGw + umask 022 + cd /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build + '[' 1 -eq 1 ']' + '[' /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/BUILDROOT '!=' / ']' + rm -rf /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/BUILDROOT ++ dirname /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/BUILDROOT + mkdir -p /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build + mkdir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/BUILDROOT + CFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CFLAGS + CXXFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CXXFLAGS + FFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FFLAGS + FCFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--build-id=sha1 -Wl,--enable-new-dtags -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd error-chain-0.12.4 + '[' 1 -eq 1 ']' + set -euo pipefail ++ /usr/bin/cargo2rpm --path Cargo.toml is-lib + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' ++ /usr/bin/cargo2rpm --path Cargo.toml name + CRATE_NAME=error-chain ++ /usr/bin/cargo2rpm --path Cargo.toml version + CRATE_VERSION=0.12.4 + REG_DIR=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/BUILDROOT/usr/share/cargo/registry/error-chain-0.12.4 + /usr/bin/mkdir -p /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/BUILDROOT/usr/share/cargo/registry/error-chain-0.12.4 + /usr/bin/awk -i inplace -v INPLACE_SUFFIX=.deps '/^\[((.+\.)?((dev|build)-)?dependencies|features)/{f=1;next} /^\[/{f=0}; !f' Cargo.toml + /usr/bin/env CARGO_HOME=.cargo RUSTC_BOOTSTRAP=1 'RUSTFLAGS=-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn' /usr/bin/cargo package -l + grep -w -E -v 'Cargo.(lock|toml.orig)' + xargs -d '\n' /usr/bin/cp --parents -a -t /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/BUILDROOT/usr/share/cargo/registry/error-chain-0.12.4 warning: no (git) VCS found for `/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4` + /usr/bin/mv Cargo.toml.deps Cargo.toml + /usr/bin/cp -a Cargo.toml /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/BUILDROOT/usr/share/cargo/registry/error-chain-0.12.4/Cargo.toml + /usr/bin/rm -f /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/BUILDROOT/usr/share/cargo/registry/error-chain-0.12.4/Cargo.toml.deps + echo '{"files":{},"package":""}' ++ /usr/bin/cargo2rpm --path Cargo.toml is-bin + '[' 0 -eq 1 ']' + /usr/lib/rpm/check-buildroot + '[' -n '' ']' + /usr/share/spec-helper/clean_files + '[' -n '' ']' + /usr/share/spec-helper/compress_files .xz + '[' -n '' ']' + /usr/share/spec-helper/relink_symlinks + '[' -n '' ']' + /usr/share/spec-helper/clean_perl + '[' -n '' ']' + /usr/share/spec-helper/lib_symlinks + '[' -n '' ']' + /usr/share/spec-helper/gprintify + '[' -n '' ']' + /usr/share/spec-helper/fix_mo + '[' -n '' ']' + /usr/share/spec-helper/fix_pamd + '[' -n '' ']' + /usr/share/spec-helper/remove_info_dir + '[' -n '' ']' + /usr/share/spec-helper/fix_eol + '[' -n '' ']' + /usr/share/spec-helper/check_desktop_files + '[' -n '' ']' + /usr/share/spec-helper/check_elf_files + /usr/lib/rpm/brp-strip /usr/bin/strip + /usr/lib/rpm/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump + /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/check-rpaths + /usr/lib/rpm/brp-remove-la-files + /usr/lib/rpm/redhat/brp-mangle-shebangs + env -u SOURCE_DATE_EPOCH /usr/lib/rpm/redhat/brp-python-bytecompile '' 1 0 -j16 + /usr/lib/rpm/redhat/brp-python-hardlink Executing(%check): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.OrU21M + umask 022 + cd /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build + CFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CFLAGS + CXXFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CXXFLAGS + FFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FFLAGS + FCFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--build-id=sha1 -Wl,--enable-new-dtags -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd error-chain-0.12.4 + '[' 1 -eq 1 ']' + /usr/bin/env CARGO_HOME=.cargo RUSTC_BOOTSTRAP=1 'RUSTFLAGS=-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn' /usr/bin/cargo test -j16 -Z avoid-dev-deps --profile rpm --no-fail-fast warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Fresh memchr v2.7.6 Fresh adler2 v2.0.1 Fresh gimli v0.32.3 Fresh version_check v0.9.5 Fresh object v0.37.3 Fresh libc v0.2.180 Fresh cfg-if v1.0.4 Fresh rustc-demangle v0.1.24 Fresh miniz_oxide v0.8.9 Fresh addr2line v0.25.1 Fresh backtrace v0.3.76 warning: unexpected `cfg` condition name: `has_error_source` --> src/error_chain.rs:3:11 | 3 | #[cfg(not(has_error_source))] | ^^^^^^^^^^^^^^^^ | = help: expected names are: `docsrs`, `feature`, and `test` and 31 more = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` = note: see for more information about checking conditional configuration = note: `#[warn(unexpected_cfgs)]` on by default warning: unexpected `cfg` condition name: `has_error_source` --> src/error_chain.rs:36:7 | 36 | #[cfg(has_error_source)] | ^^^^^^^^^^^^^^^^ | = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> src/error_chain.rs:73:7 | 73 | #[cfg(has_error_description_deprecated)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> src/error_chain.rs:82:11 | 82 | #[cfg(not(has_error_description_deprecated))] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> src/error_chain.rs:323:23 | 323 | #[cfg(not(has_error_description_deprecated))] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ::: src/example_generated.rs:24:5 | 24 | error_chain! {} | --------------- in this macro invocation | = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> src/error_chain.rs:323:23 | 323 | #[cfg(not(has_error_description_deprecated))] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ::: src/example_generated.rs:27:1 | 27 | / error_chain! { 28 | | links { 29 | | Inner(inner::Error, inner::ErrorKind) #[doc = "Link to another `ErrorChain`."]; ... | 38 | | } | |_- in this macro invocation | = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_source` --> src/lib.rs:581:31 | 581 | #[cfg(not(has_error_source))] | ^^^^^^^^^^^^^^^^ | = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition name: `has_error_source` --> src/lib.rs:583:27 | 583 | #[cfg(has_error_source)] | ^^^^^^^^^^^^^^^^ | = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> src/error_chain.rs:323:23 | 323 | #[cfg(not(has_error_description_deprecated))] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ::: src/lib.rs:823:5 | 823 | error_chain! {} | --------------- in this macro invocation | = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_description_deprecated)'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_description_deprecated)");` to the top of the `build.rs` = note: see for more information about checking conditional configuration = 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) warning: hiding a lifetime that's elided elsewhere is confusing --> src/lib.rs:615:13 | 615 | fn iter(&self) -> Iter; | ^^^^^ ^^^^ the same lifetime is hidden here | | | the lifetime is elided here | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default help: use `'_` for type paths | 615 | fn iter(&self) -> Iter<'_>; | ++++ warning: hiding a lifetime that's elided elsewhere is confusing --> src/error_chain.rs:244:21 | 244 | fn iter(&self) -> $crate::Iter { | ^^^^^ ^^^^^^^^^^^^ the same lifetime is hidden here | | | the lifetime is elided here | ::: src/example_generated.rs:27:1 | 27 | / error_chain! { 28 | | links { 29 | | Inner(inner::Error, inner::ErrorKind) #[doc = "Link to another `ErrorChain`."]; ... | 38 | | } | |_- in this macro invocation | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing = 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) help: use `'_` for type paths | 244 | fn iter(&self) -> $crate::Iter<'_> { | ++++ warning: hiding a lifetime that's elided elsewhere is confusing --> src/error_chain.rs:300:25 | 300 | pub fn iter(&self) -> $crate::Iter { | ^^^^^ ^^^^^^^^^^^^ the same lifetime is hidden here | | | the lifetime is elided here | ::: src/example_generated.rs:27:1 | 27 | / error_chain! { 28 | | links { 29 | | Inner(inner::Error, inner::ErrorKind) #[doc = "Link to another `ErrorChain`."]; ... | 38 | | } | |_- in this macro invocation | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing = 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) help: use `'_` for type paths | 300 | pub fn iter(&self) -> $crate::Iter<'_> { | ++++ warning: hiding a lifetime that's elided elsewhere is confusing --> src/error_chain.rs:244:21 | 244 | fn iter(&self) -> $crate::Iter { | ^^^^^ ^^^^^^^^^^^^ the same lifetime is hidden here | | | the lifetime is elided here | ::: src/example_generated.rs:24:5 | 24 | error_chain! {} | --------------- in this macro invocation | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing = 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) help: use `'_` for type paths | 244 | fn iter(&self) -> $crate::Iter<'_> { | ++++ warning: hiding a lifetime that's elided elsewhere is confusing --> src/error_chain.rs:300:25 | 300 | pub fn iter(&self) -> $crate::Iter { | ^^^^^ ^^^^^^^^^^^^ the same lifetime is hidden here | | | the lifetime is elided here | ::: src/example_generated.rs:24:5 | 24 | error_chain! {} | --------------- in this macro invocation | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing = 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) help: use `'_` for type paths | 300 | pub fn iter(&self) -> $crate::Iter<'_> { | ++++ warning: hiding a lifetime that's elided elsewhere is confusing --> src/error_chain.rs:244:21 | 244 | fn iter(&self) -> $crate::Iter { | ^^^^^ ^^^^^^^^^^^^ the same lifetime is hidden here | | | the lifetime is elided here | ::: src/lib.rs:823:5 | 823 | error_chain! {} | --------------- in this macro invocation | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing = 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) help: use `'_` for type paths | 244 | fn iter(&self) -> $crate::Iter<'_> { | ++++ warning: hiding a lifetime that's elided elsewhere is confusing --> src/error_chain.rs:300:25 | 300 | pub fn iter(&self) -> $crate::Iter { | ^^^^^ ^^^^^^^^^^^^ the same lifetime is hidden here | | | the lifetime is elided here | ::: src/lib.rs:823:5 | 823 | error_chain! {} | --------------- in this macro invocation | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing = 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) help: use `'_` for type paths | 300 | pub fn iter(&self) -> $crate::Iter<'_> { | ++++ Compiling error-chain v0.12.4 (/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4) warning: `error-chain` (lib) generated 16 warnings (run `cargo fix --lib -p error-chain` to apply 7 suggestions) Running `/usr/bin/rustc --crate-name error_chain --edition=2015 src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --emit=dep-info,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --test --cfg 'feature="backtrace"' --cfg 'feature="default"' --cfg 'feature="example_generated"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("backtrace", "default", "example_generated"))' -C metadata=1cf69bcadf998c1a -C extra-filename=-73ed67f38f29cf06 --out-dir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --extern backtrace=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/libbacktrace-43a9dacd75640d3f.rlib -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn --cfg has_error_source --cfg has_error_description_deprecated --cfg 'build="release"'` Running `/usr/bin/rustc --crate-name quickstart --edition=2015 examples/quickstart.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --cfg 'feature="backtrace"' --cfg 'feature="default"' --cfg 'feature="example_generated"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("backtrace", "default", "example_generated"))' -C metadata=ab1b852955c25e44 -C extra-filename=-f6aa62d62bf63b7e --out-dir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/examples -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --extern backtrace=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/libbacktrace-43a9dacd75640d3f.rlib --extern error_chain=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/liberror_chain-818d6de54d5481db.rlib -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn --cfg has_error_source --cfg has_error_description_deprecated --cfg 'build="release"'` Running `/usr/bin/rustc --crate-name size --edition=2015 examples/size.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --cfg 'feature="backtrace"' --cfg 'feature="default"' --cfg 'feature="example_generated"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("backtrace", "default", "example_generated"))' -C metadata=124a8e47c08cc146 -C extra-filename=-bd7c60c83236ab84 --out-dir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/examples -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --extern backtrace=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/libbacktrace-43a9dacd75640d3f.rlib --extern error_chain=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/liberror_chain-818d6de54d5481db.rlib -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn --cfg has_error_source --cfg has_error_description_deprecated --cfg 'build="release"'` Running `/usr/bin/rustc --crate-name all --edition=2015 examples/all.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --cfg 'feature="backtrace"' --cfg 'feature="default"' --cfg 'feature="example_generated"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("backtrace", "default", "example_generated"))' -C metadata=66c8903f04acedb4 -C extra-filename=-f660131a54755888 --out-dir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/examples -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --extern backtrace=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/libbacktrace-43a9dacd75640d3f.rlib --extern error_chain=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/liberror_chain-818d6de54d5481db.rlib -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn --cfg has_error_source --cfg has_error_description_deprecated --cfg 'build="release"'` Running `/usr/bin/rustc --crate-name has_backtrace --edition=2015 examples/has_backtrace.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --cfg 'feature="backtrace"' --cfg 'feature="default"' --cfg 'feature="example_generated"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("backtrace", "default", "example_generated"))' -C metadata=1e07d8bb80232fd0 -C extra-filename=-9d3ea37599a50038 --out-dir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/examples -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --extern backtrace=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/libbacktrace-43a9dacd75640d3f.rlib --extern error_chain=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/liberror_chain-818d6de54d5481db.rlib -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn --cfg has_error_source --cfg has_error_description_deprecated --cfg 'build="release"'` Running `/usr/bin/rustc --crate-name chain_err --edition=2015 examples/chain_err.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --cfg 'feature="backtrace"' --cfg 'feature="default"' --cfg 'feature="example_generated"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("backtrace", "default", "example_generated"))' -C metadata=970c19f84f89d0b9 -C extra-filename=-6d2fb6565be92701 --out-dir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/examples -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --extern backtrace=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/libbacktrace-43a9dacd75640d3f.rlib --extern error_chain=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/liberror_chain-818d6de54d5481db.rlib -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn --cfg has_error_source --cfg has_error_description_deprecated --cfg 'build="release"'` Running `/usr/bin/rustc --crate-name tests --edition=2015 tests/tests.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --emit=dep-info,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --test --cfg 'feature="backtrace"' --cfg 'feature="default"' --cfg 'feature="example_generated"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("backtrace", "default", "example_generated"))' -C metadata=14b95706a1c36426 -C extra-filename=-e6d7bdf9f52d8e22 --out-dir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --extern backtrace=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/libbacktrace-43a9dacd75640d3f.rlib --extern error_chain=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/liberror_chain-818d6de54d5481db.rlib -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn --cfg has_error_source --cfg has_error_description_deprecated --cfg 'build="release"'` Running `/usr/bin/rustc --crate-name quick_main --edition=2015 tests/quick_main.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --emit=dep-info,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --test --cfg 'feature="backtrace"' --cfg 'feature="default"' --cfg 'feature="example_generated"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("backtrace", "default", "example_generated"))' -C metadata=186890eb42d6a355 -C extra-filename=-25dbf1ed1743f8e8 --out-dir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --extern backtrace=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/libbacktrace-43a9dacd75640d3f.rlib --extern error_chain=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/liberror_chain-818d6de54d5481db.rlib -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn --cfg has_error_source --cfg has_error_description_deprecated --cfg 'build="release"'` Running `/usr/bin/rustc --crate-name doc --edition=2015 examples/doc.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --cfg 'feature="backtrace"' --cfg 'feature="default"' --cfg 'feature="example_generated"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("backtrace", "default", "example_generated"))' -C metadata=12caf0c00952b345 -C extra-filename=-6456198baa785a5c --out-dir /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/examples -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --extern backtrace=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/libbacktrace-43a9dacd75640d3f.rlib --extern error_chain=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/liberror_chain-818d6de54d5481db.rlib -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn --cfg has_error_source --cfg has_error_description_deprecated --cfg 'build="release"'` warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> examples/quickstart.rs:17:5 | 17 | error_chain! {} | ^^^^^^^^^^^^^^^ | = help: expected names are: `docsrs`, `feature`, and `test` and 31 more = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = note: `#[warn(unexpected_cfgs)]` on by default = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> examples/size.rs:6:1 | 6 | / error_chain! { 7 | | errors { 8 | | AVariant 9 | | Another 10 | | } 11 | | } | |_^ | = help: expected names are: `docsrs`, `feature`, and `test` and 31 more = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = note: `#[warn(unexpected_cfgs)]` on by default = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> examples/has_backtrace.rs:8:1 | 8 | / error_chain! { 9 | | errors { 10 | | MyError 11 | | } 12 | | } | |_^ | = help: expected names are: `docsrs`, `feature`, and `test` and 31 more = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = note: `#[warn(unexpected_cfgs)]` on by default = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> examples/chain_err.rs:13:5 | 13 | / error_chain! { 14 | | foreign_links { 15 | | Io(io::Error) #[doc = "Error during IO"]; ... | 29 | | } | |_____^ | = help: expected names are: `docsrs`, `feature`, and `test` and 31 more = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = note: `#[warn(unexpected_cfgs)]` on by default = 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) warning: unexpected `cfg` condition value: `a_feature` --> examples/all.rs:8:7 | 8 | #[cfg(feature = "a_feature")] | ^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `backtrace`, `default`, and `example_generated` = help: consider adding `a_feature` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration = note: `#[warn(unexpected_cfgs)]` on by default warning: unexpected `cfg` condition value: `a_feature` --> examples/all.rs:27:59 | 27 | Feature(feature::Error, feature::ErrorKind) #[cfg(feature = "a_feature")]; | ^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `backtrace`, `default`, and `example_generated` = help: consider adding `a_feature` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> examples/all.rs:5:5 | 5 | error_chain! {} | ^^^^^^^^^^^^^^^ | = help: expected names are: `docsrs`, `feature`, and `test` and 31 more = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> examples/all.rs:13:1 | 13 | / error_chain! { 14 | | // Types generated by the macro. If empty or absent, it defaults to 15 | | // Error, ErrorKind, Result; 16 | | types { ... | 34 | | } | |_^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/quick_main.rs:5:1 | 5 | error_chain!(); | ^^^^^^^^^^^^^^ | = help: expected names are: `docsrs`, `feature`, and `test` and 31 more = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = note: `#[warn(unexpected_cfgs)]` on by default = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> examples/doc.rs:10:5 | 10 | error_chain! {} | ^^^^^^^^^^^^^^^ | = help: expected names are: `docsrs`, `feature`, and `test` and 31 more = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = note: `#[warn(unexpected_cfgs)]` on by default = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> examples/doc.rs:13:1 | 13 | / error_chain! { 14 | | links { 15 | | Inner(inner::Error, inner::ErrorKind) #[doc = "Doc"]; ... | 26 | | } | |_^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:8:5 | 8 | / error_chain! { 9 | | types { 10 | | Error, ErrorKind, ResultExt, Result; ... | 17 | | errors { } 18 | | }; | |_____^ | = help: expected names are: `docsrs`, `feature`, and `test` and 31 more = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = note: `#[warn(unexpected_cfgs)]` on by default = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:23:5 | 23 | / error_chain! { 24 | | types { } 25 | | 26 | | links { } ... | 30 | | errors { } 31 | | }; | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:36:5 | 36 | / error_chain! { 37 | | links { } 38 | | 39 | | foreign_links { } 40 | | 41 | | errors { } 42 | | }; | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:47:5 | 47 | / error_chain! { 48 | | links { } 49 | | 50 | | foreign_links { } ... | 58 | | }; | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:63:5 | 63 | / error_chain! { 64 | | types { } 65 | | 66 | | links { } ... | 76 | | }; | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:81:5 | 81 | / error_chain! { 82 | | errors { 83 | | HttpStatus(e: u32) { 84 | | description("http request returned an unsuccessful status code") ... | 88 | | }; | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:93:5 | 93 | / error_chain! { 94 | | types { } 95 | | 96 | | foreign_links { } ... | 104 | | }; | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:109:5 | 109 | / error_chain! { 110 | | types { } 111 | | 112 | | links { } ... | 122 | | }; | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:127:5 | 127 | error_chain! { types { } links { } foreign_links { } errors { } }; | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:132:5 | 132 | error_chain! { links { } types { } foreign_links { } errors { } }; | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:137:5 | 137 | error_chain! { foreign_links { } links { } errors { } types { } }; | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:142:5 | 142 | error_chain! { errors { } types { } foreign_links { } }; | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:147:5 | 147 | error_chain! { foreign_links { } types { } }; | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:152:5 | 152 | / error_chain! { 153 | | links { } 154 | | 155 | | errors { ... | 163 | | foreign_links { } 164 | | }; | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:169:5 | 169 | / error_chain! { 170 | | links { } 171 | | 172 | | foreign_links { } ... | 177 | | }; | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:182:5 | 182 | / error_chain! { 183 | | links { } 184 | | 185 | | foreign_links { } ... | 191 | | }; | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:196:5 | 196 | error_chain! {}; | ^^^^^^^^^^^^^^^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `build` --> tests/tests.rs:205:30 | 205 | let cmd_folder = if cfg!(build = "debug") { | ^^^^^^^^^^^^^^^ | = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(build, values("debug"))'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(build, values(\"debug\"))");` to the top of the `build.rs` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition name: `build` --> tests/tests.rs:207:20 | 207 | } else if cfg!(build = "release") { | ^^^^^^^^^^^^^^^^^ | = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(build, values("release"))'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(build, values(\"release\"))");` to the top of the `build.rs` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:242:5 | 242 | / error_chain! { 243 | | foreign_links { 244 | | Fmt(fmt::Error); ... | 249 | | } | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:259:5 | 259 | / error_chain! { 260 | | errors { 261 | | Test 262 | | } 263 | | } | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:278:9 | 278 | error_chain! {} | ^^^^^^^^^^^^^^^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:281:5 | 281 | / error_chain! { 282 | | links { 283 | | Test(test::Error, test::ErrorKind); 284 | | } 285 | | } | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_source` --> tests/tests.rs:374:15 | 374 | #[cfg(not(has_error_source))] | ^^^^^^^^^^^^^^^^ | = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition name: `has_error_source` --> tests/tests.rs:384:11 | 384 | #[cfg(has_error_source)] | ^^^^^^^^^^^^^^^^ | = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition name: `has_error_source` --> tests/tests.rs:305:19 | 305 | #[cfg(not(has_error_source))] | ^^^^^^^^^^^^^^^^ | = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition name: `has_error_source` --> tests/tests.rs:310:15 | 310 | #[cfg(has_error_source)] | ^^^^^^^^^^^^^^^^ | = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition name: `has_error_source` --> tests/tests.rs:330:19 | 330 | #[cfg(not(has_error_source))] | ^^^^^^^^^^^^^^^^ | = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition name: `has_error_source` --> tests/tests.rs:335:15 | 335 | #[cfg(has_error_source)] | ^^^^^^^^^^^^^^^^ | = help: consider using a Cargo feature instead = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [lints.rust] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_error_source)'] } = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(has_error_source)");` to the top of the `build.rs` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:347:5 | 347 | / error_chain! { 348 | | types{ 349 | | Error, ErrorKind, ResultExt, Result; ... | 356 | | errors {} 357 | | } | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:436:5 | 436 | / error_chain! { 437 | | types { 438 | | Error, ErrorKind, ResultExt, Result; ... | 455 | | } | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:460:5 | 460 | / error_chain! { 461 | | types { 462 | | Error, ErrorKind, ResultExt, Result; 463 | | } 464 | | } | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:470:5 | 470 | / error_chain! { 471 | | types { 472 | | Error, ErrorKind, ResultExt; 473 | | } 474 | | } | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:481:9 | 481 | error_chain! {} | ^^^^^^^^^^^^^^^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:484:5 | 484 | / error_chain! { 485 | | links { 486 | | Inner(inner::Error, inner::ErrorKind) #[doc = "Doc"]; ... | 495 | | } | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:500:5 | 500 | / error_chain! { 501 | | types { 502 | | MyError, MyErrorKind, MyResultExt, MyResult; 503 | | } 504 | | } | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:505:5 | 505 | error_chain! {} | ^^^^^^^^^^^^^^^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:511:5 | 511 | error_chain! {} | ^^^^^^^^^^^^^^^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:517:5 | 517 | / error_chain! { 518 | | links { 519 | | Download(error_chain::mock::Error, error_chain::mock::ErrorKind); ... | 529 | | } | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:534:5 | 534 | / error_chain! { 535 | | links { } 536 | | 537 | | foreign_links { } 538 | | 539 | | errors { } 540 | | } | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:551:5 | 551 | error_chain! {} | ^^^^^^^^^^^^^^^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:566:5 | 566 | / error_chain! { 567 | | errors { 568 | | LocatingWorkingDir { 569 | | description("could not locate working directory") ... | 577 | | foreign_links { } 578 | | } | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:583:5 | 583 | / error_chain! { 584 | | errors { Foo } 585 | | } | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:602:5 | 602 | / error_chain! { 603 | | errors { Bar } 604 | | } | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:619:5 | 619 | / error_chain! { 620 | | types { 621 | | MyError, MyErrorKind, MyResultExt, MyResult; 622 | | } 623 | | } | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:639:5 | 639 | / error_chain! { 640 | | foreign_links { 641 | | VarErr(VarError); ... | 647 | | } | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:670:5 | 670 | / error_chain! { 671 | | links { } 672 | | 673 | | foreign_links { } ... | 681 | | }; | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:686:5 | 686 | / error_chain! { 687 | | links { } 688 | | 689 | | foreign_links { } ... | 697 | | }; | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition name: `has_error_description_deprecated` --> tests/tests.rs:702:5 | 702 | / error_chain! { 703 | | skip_msg_variant 704 | | 705 | | errors { ... | 711 | | } | |_____^ | = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `impl_error_chain_processed` crate for guidance on how handle this unexpected cfg = 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` = note: see for more information about checking conditional configuration = 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) warning: `#[doc(test(...)]` takes a list of attributes --> tests/tests.rs:508:7 | 508 | #[doc(test)] | ^^^^ | = note: `#[warn(invalid_doc_attributes)]` on by default warning: `error-chain` (example "doc") generated 2 warnings warning: `error-chain` (example "all") generated 4 warnings warning: `error-chain` (example "has_backtrace") generated 1 warning warning: `error-chain` (example "size") generated 1 warning warning: `error-chain` (test "quick_main") generated 1 warning warning: `error-chain` (lib test) generated 16 warnings (16 duplicates) warning: `error-chain` (example "quickstart") generated 1 warning warning: `error-chain` (example "chain_err") generated 1 warning warning: `error-chain` (test "tests") generated 50 warnings Finished `rpm` profile [optimized + debuginfo] target(s) in 1.81s Running `/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/error_chain-73ed67f38f29cf06` running 0 tests test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s Running `/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/quick_main-25dbf1ed1743f8e8` running 0 tests test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s Running `/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/tests-e6d7bdf9f52d8e22` running 38 tests test bail ... ok test chain_err ... ok test comma_in_errors_impl ... ok test empty ... ok test documentation ... ok test error_first ... ok test error_chain_err ... ok test ensure ... ok test error_patterns ... ok test foreign_link_test::finds_source ... ok test foreign_link_test::display_underlying_error ... ok test foreign_link_test::iterates ... ok test links ... ok test order_test_1 ... ok test order_test_2 ... ok test order_test_4 ... ok test order_test_3 ... ok test order_test_6 ... ok test order_test_5 ... ok test order_test_7 ... ok test result_match ... ok test rewrapping ... ok test rustup_regression ... ok test order_test_8 ... ok test skipping_msg_variant ... ok test smoke_test_1 ... ok test smoke_test_3 ... ok test smoke_test_2 ... ok test smoke_test_4 ... ok test smoke_test_5 ... ok test smoke_test_6 ... ok test smoke_test_7 ... ok test smoke_test_8 ... ok test trailing_comma_in_errors_impl ... ok test types_declarations ... ok test with_result ... ok test without_result ... ok test has_backtrace_depending_on_env ... ok test result: ok. 38 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.04s Doc-tests error_chain Running `/usr/bin/rustdoc --edition=2015 --crate-type lib --color auto --crate-name error_chain --test src/lib.rs --test-run-directory /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4 -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps -L dependency=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps --extern backtrace=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/libbacktrace-43a9dacd75640d3f.rlib --extern error_chain=/home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/error-chain-0.12.4/target/rpm/deps/liberror_chain-818d6de54d5481db.rlib -C embed-bitcode=no --cfg 'feature="backtrace"' --cfg 'feature="default"' --cfg 'feature="example_generated"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("backtrace", "default", "example_generated"))' --cfg has_error_source --cfg has_error_description_deprecated --cfg 'build="release"' --error-format human` running 20 tests test src/lib.rs - bail (line 726) ... ok test src/lib.rs - (line 198) ... ok test src/quick_main.rs - quick_main::quick_main (line 18) ... ok test src/lib.rs - bail (line 760) ... ok test src/lib.rs - bail (line 740) ... ok test src/lib.rs - (line 242) ... ok test src/lib.rs - (line 221) ... ok test src/lib.rs - (line 187) ... ok test src/quick_main.rs - quick_main::quick_main (line 30) ... ok test src/lib.rs - (line 269) ... ok test src/quick_main.rs - quick_main::quick_main (line 4) ... ok test src/lib.rs - bail (line 714) ... ok test src/lib.rs - ensure (line 792) ... ok test src/lib.rs - (line 295) ... ok test src/lib.rs - (line 311) ... ok test src/lib.rs - (line 102) ... ok test src/lib.rs - (line 339) ... ok test src/lib.rs - (line 361) ... ok test src/lib.rs - (line 395) ... ok test src/lib.rs - (line 471) ... ok test result: ok. 20 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.37s + RPM_EC=0 ++ jobs -p + exit 0 Processing files: rust-error-chain-devel-0.12.4-0.2.mga10.noarch warning: File listed twice: /usr/share/cargo/registry/error-chain-0.12.4/CHANGELOG.md warning: File listed twice: /usr/share/cargo/registry/error-chain-0.12.4/LICENSE-APACHE warning: File listed twice: /usr/share/cargo/registry/error-chain-0.12.4/LICENSE-MIT warning: File listed twice: /usr/share/cargo/registry/error-chain-0.12.4/README.md Provides: crate(error-chain) = 0.12.4 rust-error-chain-devel = 0.12.4-0.2.mga10 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: cargo crate(version_check/default) >= 0.9.0 Processing files: rust-error-chain+default-devel-0.12.4-0.2.mga10.noarch Provides: crate(error-chain/default) = 0.12.4 rust-error-chain+default-devel = 0.12.4-0.2.mga10 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: cargo crate(error-chain) = 0.12.4 crate(error-chain/backtrace) = 0.12.4 crate(error-chain/example_generated) = 0.12.4 Processing files: rust-error-chain+backtrace-devel-0.12.4-0.2.mga10.noarch Provides: crate(error-chain/backtrace) = 0.12.4 rust-error-chain+backtrace-devel = 0.12.4-0.2.mga10 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: cargo crate(backtrace/default) >= 0.3.3 crate(error-chain) = 0.12.4 Processing files: rust-error-chain+example_generated-devel-0.12.4-0.2.mga10.noarch Provides: crate(error-chain/example_generated) = 0.12.4 rust-error-chain+example_generated-devel = 0.12.4-0.2.mga10 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: cargo crate(error-chain) = 0.12.4 Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build/BUILDROOT Wrote: /home/pterjan/rpmbuild/RPMS/noarch/rust-error-chain+backtrace-devel-0.12.4-0.2.mga10.noarch.rpm Wrote: /home/pterjan/rpmbuild/RPMS/noarch/rust-error-chain+default-devel-0.12.4-0.2.mga10.noarch.rpm Wrote: /home/pterjan/rpmbuild/RPMS/noarch/rust-error-chain+example_generated-devel-0.12.4-0.2.mga10.noarch.rpm Wrote: /home/pterjan/rpmbuild/RPMS/noarch/rust-error-chain-devel-0.12.4-0.2.mga10.noarch.rpm Executing(rmbuild): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.xlcMZY + umask 022 + cd /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build + test -d /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build + rm -rf /home/pterjan/rpmbuild/BUILD/rust-error-chain-0.12.4-build + RPM_EC=0 ++ jobs -p + exit 0 RPM build warnings: File listed twice: /usr/share/cargo/registry/error-chain-0.12.4/CHANGELOG.md File listed twice: /usr/share/cargo/registry/error-chain-0.12.4/LICENSE-APACHE File listed twice: /usr/share/cargo/registry/error-chain-0.12.4/LICENSE-MIT File listed twice: /usr/share/cargo/registry/error-chain-0.12.4/README.md D: [iurt_root_command] Success!