Nov 17 21:57:14.805 INFO testing ssh2-0.3.3 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982 Nov 17 21:57:14.807 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-1/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-alt build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"` Nov 17 21:57:15.305 INFO [stdout] fcb8b4a2a4b9b6af5f06fd02899bd647561a2f8568839b59563aebadd13726b0 Nov 17 21:57:15.307 INFO running `"docker" "start" "-a" "fcb8b4a2a4b9b6af5f06fd02899bd647561a2f8568839b59563aebadd13726b0"` Nov 17 21:57:17.111 INFO [stderr] usermod: no changes Nov 17 21:57:17.139 INFO [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently Nov 17 21:57:17.139 INFO [stderr] disables Cargo from automatically inferring other test targets. Nov 17 21:57:17.139 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 17 21:57:17.139 INFO [stderr] files will be included as a test target: Nov 17 21:57:17.139 INFO [stderr] Nov 17 21:57:17.139 INFO [stderr] * /source/tests/session.rs Nov 17 21:57:17.139 INFO [stderr] * /source/tests/channel.rs Nov 17 21:57:17.139 INFO [stderr] * /source/tests/knownhosts.rs Nov 17 21:57:17.139 INFO [stderr] * /source/tests/sftp.rs Nov 17 21:57:17.139 INFO [stderr] * /source/tests/agent.rs Nov 17 21:57:17.139 INFO [stderr] Nov 17 21:57:17.139 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 17 21:57:17.139 INFO [stderr] ready to be compiled as a test target today. You can future-proof yourself Nov 17 21:57:17.139 INFO [stderr] and disable this warning by adding `autotests = false` to your [package] Nov 17 21:57:17.139 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 17 21:57:17.139 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 17 21:57:17.139 INFO [stderr] Nov 17 21:57:17.139 INFO [stderr] For more information on this warning you can consult Nov 17 21:57:17.139 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 17 21:57:17.211 INFO [stderr] Compiling ssh2 v0.3.3 (/source) Nov 17 21:57:18.871 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 1.74s Nov 17 21:57:18.877 INFO [stderr] su: No module specific data is present Nov 17 21:57:19.541 INFO running `"docker" "inspect" "fcb8b4a2a4b9b6af5f06fd02899bd647561a2f8568839b59563aebadd13726b0"` Nov 17 21:57:19.759 INFO running `"docker" "rm" "-f" "fcb8b4a2a4b9b6af5f06fd02899bd647561a2f8568839b59563aebadd13726b0"` Nov 17 21:57:20.051 INFO [stdout] fcb8b4a2a4b9b6af5f06fd02899bd647561a2f8568839b59563aebadd13726b0 Nov 17 21:57:20.056 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-1/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-alt test --frozen --no-run" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"` Nov 17 21:57:20.468 INFO [stdout] c27cff2434f0eeb25ada374ca11f7899ac34141b24950ac559e25e4c88e22f04 Nov 17 21:57:20.470 INFO running `"docker" "start" "-a" "c27cff2434f0eeb25ada374ca11f7899ac34141b24950ac559e25e4c88e22f04"` Nov 17 21:57:22.459 INFO [stderr] usermod: no changes Nov 17 21:57:22.525 INFO [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently Nov 17 21:57:22.525 INFO [stderr] disables Cargo from automatically inferring other test targets. Nov 17 21:57:22.525 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 17 21:57:22.525 INFO [stderr] files will be included as a test target: Nov 17 21:57:22.525 INFO [stderr] Nov 17 21:57:22.525 INFO [stderr] * /source/tests/session.rs Nov 17 21:57:22.525 INFO [stderr] * /source/tests/channel.rs Nov 17 21:57:22.525 INFO [stderr] * /source/tests/knownhosts.rs Nov 17 21:57:22.525 INFO [stderr] * /source/tests/sftp.rs Nov 17 21:57:22.525 INFO [stderr] * /source/tests/agent.rs Nov 17 21:57:22.526 INFO [stderr] Nov 17 21:57:22.526 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 17 21:57:22.526 INFO [stderr] ready to be compiled as a test target today. You can future-proof yourself Nov 17 21:57:22.526 INFO [stderr] and disable this warning by adding `autotests = false` to your [package] Nov 17 21:57:22.526 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 17 21:57:22.526 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 17 21:57:22.526 INFO [stderr] Nov 17 21:57:22.526 INFO [stderr] For more information on this warning you can consult Nov 17 21:57:22.526 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 17 21:57:22.603 INFO [stderr] Compiling ssh2 v0.3.3 (/source) Nov 17 21:57:25.760 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 3.27s Nov 17 21:57:25.779 INFO [stderr] su: No module specific data is present Nov 17 21:57:26.510 INFO running `"docker" "inspect" "c27cff2434f0eeb25ada374ca11f7899ac34141b24950ac559e25e4c88e22f04"` Nov 17 21:57:26.891 INFO running `"docker" "rm" "-f" "c27cff2434f0eeb25ada374ca11f7899ac34141b24950ac559e25e4c88e22f04"` Nov 17 21:57:27.239 INFO [stdout] c27cff2434f0eeb25ada374ca11f7899ac34141b24950ac559e25e4c88e22f04