[INFO] crate xmlrpc 0.13.1 is already in cache [INFO] checking xmlrpc-0.13.1 against try#e922e6444795ab795fab1943288aee3d543699b8 for pr-66852 [INFO] extracting crate xmlrpc 0.13.1 into /workspace/builds/worker-3/source [INFO] validating manifest of crates.io crate xmlrpc 0.13.1 on toolchain e922e6444795ab795fab1943288aee3d543699b8 [INFO] running `"/workspace/cargo-home/bin/cargo" "+e922e6444795ab795fab1943288aee3d543699b8" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] started tweaking crates.io crate xmlrpc 0.13.1 [INFO] removed 2 missing examples [INFO] removed 2 missing tests [INFO] finished tweaking crates.io crate xmlrpc 0.13.1 [INFO] tweaked toml for crates.io crate xmlrpc 0.13.1 written to /workspace/builds/worker-3/source/Cargo.toml [INFO] running `"/workspace/cargo-home/bin/cargo" "+e922e6444795ab795fab1943288aee3d543699b8" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/workspace/cargo-home/bin/cargo" "+e922e6444795ab795fab1943288aee3d543699b8" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] [stderr] warning: An explicit [[example]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other example targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a example target: [INFO] [stderr] [INFO] [stderr] * /workspace/builds/worker-3/source/examples/custom-header.rs [INFO] [stderr] * /workspace/builds/worker-3/source/examples/client.rs [INFO] [stderr] [INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be [INFO] [stderr] ready to be compiled as a example target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autoexamples = false` to your [package] [INFO] [stderr] section. You may also move the files to a location where Cargo would not [INFO] [stderr] automatically infer them to be a target, such as in subfolders. [INFO] [stderr] [INFO] [stderr] For more information on this warning you can consult [INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330 [INFO] [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other test targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a test target: [INFO] [stderr] [INFO] [stderr] * /workspace/builds/worker-3/source/tests/python.rs [INFO] [stderr] * /workspace/builds/worker-3/source/tests/version-numbers.rs [INFO] [stderr] [INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be [INFO] [stderr] ready to be compiled as a test target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autotests = false` to your [package] [INFO] [stderr] section. You may also move the files to a location where Cargo would not [INFO] [stderr] automatically infer them to be a target, such as in subfolders. [INFO] [stderr] [INFO] [stderr] For more information on this warning you can consult [INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330 [INFO] running `"docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "MAP_USER_ID=0" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--network" "none" "rustops/crates-build-env" "/opt/rustwide/cargo-home/bin/cargo" "+e922e6444795ab795fab1943288aee3d543699b8" "check" "--frozen" "--all" "--all-targets"` [INFO] [stdout] b9b85f6eb34bf52848f9845fc7cff72fee7c14013ac7656e95f97b3ca0f0cb8a [INFO] [stderr] WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap. [INFO] running `"docker" "start" "-a" "b9b85f6eb34bf52848f9845fc7cff72fee7c14013ac7656e95f97b3ca0f0cb8a"` [INFO] [stderr] warning: An explicit [[example]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other example targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a example target: [INFO] [stderr] [INFO] [stderr] * /opt/rustwide/workdir/examples/custom-header.rs [INFO] [stderr] * /opt/rustwide/workdir/examples/client.rs [INFO] [stderr] [INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be [INFO] [stderr] ready to be compiled as a example target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autoexamples = false` to your [package] [INFO] [stderr] section. You may also move the files to a location where Cargo would not [INFO] [stderr] automatically infer them to be a target, such as in subfolders. [INFO] [stderr] [INFO] [stderr] For more information on this warning you can consult [INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330 [INFO] [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other test targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a test target: [INFO] [stderr] [INFO] [stderr] * /opt/rustwide/workdir/tests/python.rs [INFO] [stderr] * /opt/rustwide/workdir/tests/version-numbers.rs [INFO] [stderr] [INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be [INFO] [stderr] ready to be compiled as a test target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autotests = false` to your [package] [INFO] [stderr] section. You may also move the files to a location where Cargo would not [INFO] [stderr] automatically infer them to be a target, such as in subfolders. [INFO] [stderr] [INFO] [stderr] For more information on this warning you can consult [INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330 [INFO] [stderr] Checking try_from v0.3.2 [INFO] [stderr] Checking cookie v0.12.0 [INFO] [stderr] Checking tokio-io v0.1.12 [INFO] [stderr] Checking http v0.1.21 [INFO] [stderr] Checking tokio-buf v0.1.1 [INFO] [stderr] Checking string v0.2.1 [INFO] [stderr] Checking syn v0.15.44 [INFO] [stderr] Checking iso8601 v0.2.0 [INFO] [stderr] error[E0277]: `?` couldn't convert the error to `char::TryFromIntToCharError` [INFO] [stderr] --> /opt/rustwide/cargo-home/registry/src/github.com-1ecc6299db9ec823/try_from-0.3.2/src/char.rs:56:39 [INFO] [stderr] | [INFO] [stderr] 56 | match u32::try_from(n)? { [INFO] [stderr] | ^ the trait `std::convert::From` is not implemented for `char::TryFromIntToCharError` [INFO] [stderr] ... [INFO] [stderr] 68 | impl_int_to_char!(i8, i16, i32, i64, isize, u16, u32, u64, usize); [INFO] [stderr] | ------------------------------------------------------------------ in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait [INFO] [stderr] = help: the following implementations were found: [INFO] [stderr] > [INFO] [stderr] > [INFO] [stderr] = note: required by `std::convert::From::from` [INFO] [stderr] [INFO] [stderr] error[E0277]: `?` couldn't convert the error to `char::TryFromIntToCharError` [INFO] [stderr] --> /opt/rustwide/cargo-home/registry/src/github.com-1ecc6299db9ec823/try_from-0.3.2/src/char.rs:56:39 [INFO] [stderr] | [INFO] [stderr] 56 | match u32::try_from(n)? { [INFO] [stderr] | ^ the trait `std::convert::From` is not implemented for `char::TryFromIntToCharError` [INFO] [stderr] ... [INFO] [stderr] 68 | impl_int_to_char!(i8, i16, i32, i64, isize, u16, u32, u64, usize); [INFO] [stderr] | ------------------------------------------------------------------ in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait [INFO] [stderr] = help: the following implementations were found: [INFO] [stderr] > [INFO] [stderr] > [INFO] [stderr] = note: required by `std::convert::From::from` [INFO] [stderr] [INFO] [stderr] error[E0277]: `?` couldn't convert the error to `char::TryFromIntToCharError` [INFO] [stderr] --> /opt/rustwide/cargo-home/registry/src/github.com-1ecc6299db9ec823/try_from-0.3.2/src/char.rs:56:39 [INFO] [stderr] | [INFO] [stderr] 56 | match u32::try_from(n)? { [INFO] [stderr] | ^ the trait `std::convert::From` is not implemented for `char::TryFromIntToCharError` [INFO] [stderr] ... [INFO] [stderr] 68 | impl_int_to_char!(i8, i16, i32, i64, isize, u16, u32, u64, usize); [INFO] [stderr] | ------------------------------------------------------------------ in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait [INFO] [stderr] = help: the following implementations were found: [INFO] [stderr] > [INFO] [stderr] > [INFO] [stderr] = note: required by `std::convert::From::from` [INFO] [stderr] [INFO] [stderr] error[E0277]: `?` couldn't convert the error to `char::TryFromIntToCharError` [INFO] [stderr] --> /opt/rustwide/cargo-home/registry/src/github.com-1ecc6299db9ec823/try_from-0.3.2/src/char.rs:56:39 [INFO] [stderr] | [INFO] [stderr] 56 | match u32::try_from(n)? { [INFO] [stderr] | ^ the trait `std::convert::From` is not implemented for `char::TryFromIntToCharError` [INFO] [stderr] ... [INFO] [stderr] 68 | impl_int_to_char!(i8, i16, i32, i64, isize, u16, u32, u64, usize); [INFO] [stderr] | ------------------------------------------------------------------ in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait [INFO] [stderr] = help: the following implementations were found: [INFO] [stderr] > [INFO] [stderr] > [INFO] [stderr] = note: required by `std::convert::From::from` [INFO] [stderr] [INFO] [stderr] error[E0277]: `?` couldn't convert the error to `char::TryFromIntToCharError` [INFO] [stderr] --> /opt/rustwide/cargo-home/registry/src/github.com-1ecc6299db9ec823/try_from-0.3.2/src/char.rs:56:39 [INFO] [stderr] | [INFO] [stderr] 56 | match u32::try_from(n)? { [INFO] [stderr] | ^ the trait `std::convert::From` is not implemented for `char::TryFromIntToCharError` [INFO] [stderr] ... [INFO] [stderr] 68 | impl_int_to_char!(i8, i16, i32, i64, isize, u16, u32, u64, usize); [INFO] [stderr] | ------------------------------------------------------------------ in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait [INFO] [stderr] = help: the following implementations were found: [INFO] [stderr] > [INFO] [stderr] > [INFO] [stderr] = note: required by `std::convert::From::from` [INFO] [stderr] [INFO] [stderr] error[E0277]: `?` couldn't convert the error to `char::TryFromIntToCharError` [INFO] [stderr] --> /opt/rustwide/cargo-home/registry/src/github.com-1ecc6299db9ec823/try_from-0.3.2/src/char.rs:56:39 [INFO] [stderr] | [INFO] [stderr] 56 | match u32::try_from(n)? { [INFO] [stderr] | ^ the trait `std::convert::From<()>` is not implemented for `char::TryFromIntToCharError` [INFO] [stderr] ... [INFO] [stderr] 68 | impl_int_to_char!(i8, i16, i32, i64, isize, u16, u32, u64, usize); [INFO] [stderr] | ------------------------------------------------------------------ in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait [INFO] [stderr] = help: the following implementations were found: [INFO] [stderr] > [INFO] [stderr] > [INFO] [stderr] = note: required by `std::convert::From::from` [INFO] [stderr] [INFO] [stderr] error[E0277]: `?` couldn't convert the error to `char::TryFromIntToCharError` [INFO] [stderr] --> /opt/rustwide/cargo-home/registry/src/github.com-1ecc6299db9ec823/try_from-0.3.2/src/char.rs:56:39 [INFO] [stderr] | [INFO] [stderr] 56 | match u32::try_from(n)? { [INFO] [stderr] | ^ the trait `std::convert::From<()>` is not implemented for `char::TryFromIntToCharError` [INFO] [stderr] ... [INFO] [stderr] 68 | impl_int_to_char!(i8, i16, i32, i64, isize, u16, u32, u64, usize); [INFO] [stderr] | ------------------------------------------------------------------ in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait [INFO] [stderr] = help: the following implementations were found: [INFO] [stderr] > [INFO] [stderr] > [INFO] [stderr] = note: required by `std::convert::From::from` [INFO] [stderr] [INFO] [stderr] Checking uuid v0.7.4 [INFO] [stderr] error[E0277]: `?` couldn't convert the error to `char::TryFromIntToCharError` [INFO] [stderr] --> /opt/rustwide/cargo-home/registry/src/github.com-1ecc6299db9ec823/try_from-0.3.2/src/char.rs:56:39 [INFO] [stderr] | [INFO] [stderr] 56 | match u32::try_from(n)? { [INFO] [stderr] | ^ the trait `std::convert::From` is not implemented for `char::TryFromIntToCharError` [INFO] [stderr] ... [INFO] [stderr] 68 | impl_int_to_char!(i8, i16, i32, i64, isize, u16, u32, u64, usize); [INFO] [stderr] | ------------------------------------------------------------------ in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait [INFO] [stderr] = help: the following implementations were found: [INFO] [stderr] > [INFO] [stderr] > [INFO] [stderr] = note: required by `std::convert::From::from` [INFO] [stderr] [INFO] [stderr] error[E0277]: `?` couldn't convert the error to `char::TryFromIntToCharError` [INFO] [stderr] --> /opt/rustwide/cargo-home/registry/src/github.com-1ecc6299db9ec823/try_from-0.3.2/src/char.rs:56:39 [INFO] [stderr] | [INFO] [stderr] 56 | match u32::try_from(n)? { [INFO] [stderr] | ^ the trait `std::convert::From` is not implemented for `char::TryFromIntToCharError` [INFO] [stderr] ... [INFO] [stderr] 68 | impl_int_to_char!(i8, i16, i32, i64, isize, u16, u32, u64, usize); [INFO] [stderr] | ------------------------------------------------------------------ in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait [INFO] [stderr] = help: the following implementations were found: [INFO] [stderr] > [INFO] [stderr] > [INFO] [stderr] = note: required by `std::convert::From::from` [INFO] [stderr] [INFO] [stderr] error: aborting due to 9 previous errors [INFO] [stderr] [INFO] [stderr] For more information about this error, try `rustc --explain E0277`. [INFO] [stderr] error: could not compile `try_from`. [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] [stderr] error: build failed [INFO] running `"docker" "inspect" "b9b85f6eb34bf52848f9845fc7cff72fee7c14013ac7656e95f97b3ca0f0cb8a"` [INFO] running `"docker" "rm" "-f" "b9b85f6eb34bf52848f9845fc7cff72fee7c14013ac7656e95f97b3ca0f0cb8a"` [INFO] [stdout] b9b85f6eb34bf52848f9845fc7cff72fee7c14013ac7656e95f97b3ca0f0cb8a