Dec 01 09:31:53.652 INFO testing mersinvald/batch_resolve against 1.30.1 for beta-1.31-5
Dec 01 09:31:53.652 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-2/1.30.1:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/beta-1.31-5/1.30.1:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +1.30.1 build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 01 09:31:54.174 INFO [stdout] 11e805f2f7b2f96174f8f324e3b198b8e40cdf08e795cdbcb9f96cb63cab1c37
Dec 01 09:31:54.176 INFO running `"docker" "start" "-a" "11e805f2f7b2f96174f8f324e3b198b8e40cdf08e795cdbcb9f96cb63cab1c37"`
Dec 01 09:31:55.235 INFO [stderr] usermod: no changes
Dec 01 09:31:55.268 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 01 09:31:55.268 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 01 09:31:55.268 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 01 09:31:55.268 INFO [stderr] files will be included as a binary target:
Dec 01 09:31:55.268 INFO [stderr] 
Dec 01 09:31:55.268 INFO [stderr] * /source/src/main.rs
Dec 01 09:31:55.268 INFO [stderr] 
Dec 01 09:31:55.268 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 01 09:31:55.268 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 01 09:31:55.268 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 01 09:31:55.268 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 01 09:31:55.268 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 01 09:31:55.268 INFO [stderr] 
Dec 01 09:31:55.268 INFO [stderr] For more information on this warning you can consult
Dec 01 09:31:55.268 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 01 09:31:55.268 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `batch_resolve`,
Dec 01 09:31:55.268 INFO [stderr] please set bin.path in Cargo.toml
Dec 01 09:31:55.461 INFO [stderr]    Compiling smallvec v0.3.3
Dec 01 09:31:55.462 INFO [stderr]    Compiling openssl v0.9.11
Dec 01 09:31:55.472 INFO [stderr]    Compiling futures v0.1.13
Dec 01 09:31:55.475 INFO [stderr]    Compiling trust-dns v0.10.1
Dec 01 09:31:55.475 INFO [stderr]    Compiling data-encoding v1.2.0
Dec 01 09:31:55.478 INFO [stderr]    Compiling serde v1.0.3
Dec 01 09:31:55.484 INFO [stderr]    Compiling iovec v0.1.0
Dec 01 09:31:55.491 INFO [stderr]    Compiling net2 v0.2.29
Dec 01 09:31:56.659 INFO [stderr]    Compiling clicolors-control v0.1.0
Dec 01 09:31:59.887 INFO [stderr]    Compiling clap v2.24.1
Dec 01 09:31:59.939 INFO [stderr]    Compiling bytes v0.4.3
Dec 01 09:31:59.959 INFO [stderr]    Compiling parking_lot_core v0.2.1
Dec 01 09:31:59.980 INFO [stderr]    Compiling backtrace-sys v0.1.10
Dec 01 09:32:00.036 INFO [stderr]    Compiling mio v0.6.7
Dec 01 09:32:00.072 INFO [stderr]    Compiling openssl-sys v0.9.11
Dec 01 09:32:01.699 INFO [stderr]    Compiling chrono v0.2.25
Dec 01 09:32:06.999 INFO [stderr]    Compiling env_logger v0.4.2
Dec 01 09:32:07.059 INFO [stderr]    Compiling backtrace v0.2.3
Dec 01 09:32:07.111 INFO [stderr]    Compiling serde_derive v1.0.3
Dec 01 09:32:14.407 INFO [stderr]    Compiling parking_lot v0.4.3
Dec 01 09:32:14.451 INFO [stderr]    Compiling error-chain v0.1.12
Dec 01 09:32:14.475 INFO [stderr]    Compiling tokio-io v0.1.1
Dec 01 09:32:18.649 INFO [stderr]    Compiling tokio-core v0.1.7
Dec 01 09:32:19.708 INFO [stderr]    Compiling indicatif v0.1.0
Dec 01 09:32:32.299 INFO [stderr]    Compiling toml v0.4.0
Dec 01 09:32:58.319 INFO [stderr]    Compiling batch_resolve_cli v0.3.5 (/source)
Dec 01 09:33:00.191 INFO [stderr] warning: use of deprecated item 'std::ascii::AsciiExt': use inherent methods instead
Dec 01 09:33:00.191 INFO [stderr]    --> src/resolve/batch.rs:110:1
Dec 01 09:33:00.191 INFO [stderr]     |
Dec 01 09:33:00.191 INFO [stderr] 110 | / arg_enum!{
Dec 01 09:33:00.191 INFO [stderr] 111 | |     #[derive(Copy, Clone, Debug)]
Dec 01 09:33:00.191 INFO [stderr] 112 | |     pub enum QueryType {
Dec 01 09:33:00.191 INFO [stderr] 113 | |         A,
Dec 01 09:33:00.191 INFO [stderr] ...   |
Dec 01 09:33:00.191 INFO [stderr] 117 | |     }
Dec 01 09:33:00.191 INFO [stderr] 118 | | }
Dec 01 09:33:00.191 INFO [stderr]     | |_^
Dec 01 09:33:00.191 INFO [stderr]     |
Dec 01 09:33:00.191 INFO [stderr]     = note: #[warn(deprecated)] on by default
Dec 01 09:33:00.191 INFO [stderr]     = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
Dec 01 09:33:00.191 INFO [stderr] 
Dec 01 09:33:09.463 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1m 14s
Dec 01 09:33:09.474 INFO [stderr] su: No module specific data is present
Dec 01 09:33:11.087 INFO running `"docker" "inspect" "11e805f2f7b2f96174f8f324e3b198b8e40cdf08e795cdbcb9f96cb63cab1c37"`
Dec 01 09:33:11.481 INFO running `"docker" "rm" "-f" "11e805f2f7b2f96174f8f324e3b198b8e40cdf08e795cdbcb9f96cb63cab1c37"`
Dec 01 09:33:11.779 INFO [stdout] 11e805f2f7b2f96174f8f324e3b198b8e40cdf08e795cdbcb9f96cb63cab1c37
Dec 01 09:33:11.781 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-2/1.30.1:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/beta-1.31-5/1.30.1:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +1.30.1 test --frozen --no-run" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 01 09:33:12.211 INFO [stdout] 51d86a10ad9980bea3c4c26de4d7a706ba9f459cd9c4ccb32f270698c3924b85
Dec 01 09:33:12.219 INFO running `"docker" "start" "-a" "51d86a10ad9980bea3c4c26de4d7a706ba9f459cd9c4ccb32f270698c3924b85"`
Dec 01 09:33:13.661 INFO [stderr] usermod: no changes
Dec 01 09:33:13.747 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 01 09:33:13.747 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 01 09:33:13.747 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 01 09:33:13.747 INFO [stderr] files will be included as a binary target:
Dec 01 09:33:13.747 INFO [stderr] 
Dec 01 09:33:13.747 INFO [stderr] * /source/src/main.rs
Dec 01 09:33:13.747 INFO [stderr] 
Dec 01 09:33:13.747 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 01 09:33:13.747 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 01 09:33:13.747 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 01 09:33:13.747 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 01 09:33:13.747 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 01 09:33:13.747 INFO [stderr] 
Dec 01 09:33:13.747 INFO [stderr] For more information on this warning you can consult
Dec 01 09:33:13.747 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 01 09:33:13.747 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `batch_resolve`,
Dec 01 09:33:13.747 INFO [stderr] please set bin.path in Cargo.toml
Dec 01 09:33:13.936 INFO [stderr]    Compiling batch_resolve_cli v0.3.5 (/source)
Dec 01 09:33:15.967 INFO [stderr] warning: use of deprecated item 'std::ascii::AsciiExt': use inherent methods instead
Dec 01 09:33:15.967 INFO [stderr]    --> src/resolve/batch.rs:110:1
Dec 01 09:33:15.967 INFO [stderr]     |
Dec 01 09:33:15.967 INFO [stderr] 110 | / arg_enum!{
Dec 01 09:33:15.967 INFO [stderr] 111 | |     #[derive(Copy, Clone, Debug)]
Dec 01 09:33:15.967 INFO [stderr] 112 | |     pub enum QueryType {
Dec 01 09:33:15.967 INFO [stderr] 113 | |         A,
Dec 01 09:33:15.967 INFO [stderr] ...   |
Dec 01 09:33:15.967 INFO [stderr] 117 | |     }
Dec 01 09:33:15.967 INFO [stderr] 118 | | }
Dec 01 09:33:15.967 INFO [stderr]     | |_^
Dec 01 09:33:15.967 INFO [stderr]     |
Dec 01 09:33:15.967 INFO [stderr]     = note: #[warn(deprecated)] on by default
Dec 01 09:33:15.967 INFO [stderr]     = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
Dec 01 09:33:15.967 INFO [stderr] 
Dec 01 09:33:17.243 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 3.53s
Dec 01 09:33:17.252 INFO [stderr] su: No module specific data is present
Dec 01 09:33:17.913 INFO running `"docker" "inspect" "51d86a10ad9980bea3c4c26de4d7a706ba9f459cd9c4ccb32f270698c3924b85"`
Dec 01 09:33:18.262 INFO running `"docker" "rm" "-f" "51d86a10ad9980bea3c4c26de4d7a706ba9f459cd9c4ccb32f270698c3924b85"`
Dec 01 09:33:18.563 INFO [stdout] 51d86a10ad9980bea3c4c26de4d7a706ba9f459cd9c4ccb32f270698c3924b85
Dec 01 09:33:18.567 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-2/1.30.1:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/beta-1.31-5/1.30.1:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +1.30.1 test --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 01 09:33:19.000 INFO [stdout] 14eaf5b0a90e9f364c6697e0a52e56c62f5ef59783fce4f54ff087d6f5471ed9
Dec 01 09:33:19.002 INFO running `"docker" "start" "-a" "14eaf5b0a90e9f364c6697e0a52e56c62f5ef59783fce4f54ff087d6f5471ed9"`
Dec 01 09:33:20.475 INFO [stderr] usermod: no changes
Dec 01 09:33:20.570 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 01 09:33:20.570 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 01 09:33:20.570 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 01 09:33:20.570 INFO [stderr] files will be included as a binary target:
Dec 01 09:33:20.570 INFO [stderr] 
Dec 01 09:33:20.570 INFO [stderr] * /source/src/main.rs
Dec 01 09:33:20.570 INFO [stderr] 
Dec 01 09:33:20.570 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 01 09:33:20.570 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 01 09:33:20.570 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 01 09:33:20.570 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 01 09:33:20.570 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 01 09:33:20.570 INFO [stderr] 
Dec 01 09:33:20.570 INFO [stderr] For more information on this warning you can consult
Dec 01 09:33:20.570 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 01 09:33:20.570 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `batch_resolve`,
Dec 01 09:33:20.570 INFO [stderr] please set bin.path in Cargo.toml
Dec 01 09:33:20.819 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.31s
Dec 01 09:33:20.826 INFO [stderr]      Running /target/debug/deps/batch_resolve-80a5fd48dd6bd3d4
Dec 01 09:33:20.834 INFO [stdout] 
Dec 01 09:33:20.834 INFO [stdout] running 0 tests
Dec 01 09:33:20.834 INFO [stdout] 
Dec 01 09:33:20.834 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 01 09:33:20.834 INFO [stdout] 
Dec 01 09:33:20.836 INFO [stderr] su: No module specific data is present
Dec 01 09:33:21.749 INFO running `"docker" "inspect" "14eaf5b0a90e9f364c6697e0a52e56c62f5ef59783fce4f54ff087d6f5471ed9"`
Dec 01 09:33:22.113 INFO running `"docker" "rm" "-f" "14eaf5b0a90e9f364c6697e0a52e56c62f5ef59783fce4f54ff087d6f5471ed9"`
Dec 01 09:33:22.415 INFO [stdout] 14eaf5b0a90e9f364c6697e0a52e56c62f5ef59783fce4f54ff087d6f5471ed9
