Nov 17 21:57:16.716 INFO testing ssh2-0.3.3 against master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c for pr-55982
Nov 17 21:57:16.716 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-0/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/pr-55982/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/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 +6b9b97bd9b704f85f0184f7a213cc4d62bd9654c-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:17.191 INFO [stdout] 603d60266fdbc3f52637270c085fbb14550983ca0357647f677b151e89548196
Nov 17 21:57:17.192 INFO running `"docker" "start" "-a" "603d60266fdbc3f52637270c085fbb14550983ca0357647f677b151e89548196"`
Nov 17 21:57:18.277 INFO [stderr] usermod: no changes
Nov 17 21:57:18.339 INFO [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently
Nov 17 21:57:18.339 INFO [stderr] disables Cargo from automatically inferring other test targets.
Nov 17 21:57:18.339 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 17 21:57:18.339 INFO [stderr] files will be included as a test target:
Nov 17 21:57:18.339 INFO [stderr] 
Nov 17 21:57:18.339 INFO [stderr] * /source/tests/session.rs
Nov 17 21:57:18.339 INFO [stderr] * /source/tests/channel.rs
Nov 17 21:57:18.339 INFO [stderr] * /source/tests/knownhosts.rs
Nov 17 21:57:18.339 INFO [stderr] * /source/tests/sftp.rs
Nov 17 21:57:18.339 INFO [stderr] * /source/tests/agent.rs
Nov 17 21:57:18.339 INFO [stderr] 
Nov 17 21:57:18.340 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 17 21:57:18.340 INFO [stderr] ready to be compiled as a test target today. You can future-proof yourself
Nov 17 21:57:18.340 INFO [stderr] and disable this warning by adding `autotests = false` to your [package]
Nov 17 21:57:18.340 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 17 21:57:18.340 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 17 21:57:18.340 INFO [stderr] 
Nov 17 21:57:18.340 INFO [stderr] For more information on this warning you can consult
Nov 17 21:57:18.340 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 17 21:57:18.377 INFO [stderr]    Compiling libssh2-sys v0.2.11
Nov 17 21:57:26.215 INFO [stderr]    Compiling ssh2 v0.3.3 (/source)
Nov 17 21:57:28.173 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 9.86s
Nov 17 21:57:28.184 INFO [stderr] su: No module specific data is present
Nov 17 21:57:29.016 INFO running `"docker" "inspect" "603d60266fdbc3f52637270c085fbb14550983ca0357647f677b151e89548196"`
Nov 17 21:57:29.330 INFO running `"docker" "rm" "-f" "603d60266fdbc3f52637270c085fbb14550983ca0357647f677b151e89548196"`
Nov 17 21:57:29.591 INFO [stdout] 603d60266fdbc3f52637270c085fbb14550983ca0357647f677b151e89548196
Nov 17 21:57:29.595 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-0/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/pr-55982/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/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 +6b9b97bd9b704f85f0184f7a213cc4d62bd9654c-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:30.071 INFO [stdout] 96f56bf9e79e451f96fa416b560ce07c78384f52d6fb76cddb5419b23882da36
Nov 17 21:57:30.074 INFO running `"docker" "start" "-a" "96f56bf9e79e451f96fa416b560ce07c78384f52d6fb76cddb5419b23882da36"`
Nov 17 21:57:31.952 INFO [stderr] usermod: no changes
Nov 17 21:57:32.026 INFO [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently
Nov 17 21:57:32.026 INFO [stderr] disables Cargo from automatically inferring other test targets.
Nov 17 21:57:32.026 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 17 21:57:32.026 INFO [stderr] files will be included as a test target:
Nov 17 21:57:32.026 INFO [stderr] 
Nov 17 21:57:32.026 INFO [stderr] * /source/tests/session.rs
Nov 17 21:57:32.026 INFO [stderr] * /source/tests/channel.rs
Nov 17 21:57:32.026 INFO [stderr] * /source/tests/knownhosts.rs
Nov 17 21:57:32.026 INFO [stderr] * /source/tests/sftp.rs
Nov 17 21:57:32.026 INFO [stderr] * /source/tests/agent.rs
Nov 17 21:57:32.026 INFO [stderr] 
Nov 17 21:57:32.026 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 17 21:57:32.026 INFO [stderr] ready to be compiled as a test target today. You can future-proof yourself
Nov 17 21:57:32.026 INFO [stderr] and disable this warning by adding `autotests = false` to your [package]
Nov 17 21:57:32.026 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 17 21:57:32.026 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 17 21:57:32.026 INFO [stderr] 
Nov 17 21:57:32.026 INFO [stderr] For more information on this warning you can consult
Nov 17 21:57:32.026 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 17 21:57:32.115 INFO [stderr]    Compiling ssh2 v0.3.3 (/source)
Nov 17 21:57:35.434 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 3.46s
Nov 17 21:57:35.443 INFO [stderr] su: No module specific data is present
Nov 17 21:57:35.975 INFO running `"docker" "inspect" "96f56bf9e79e451f96fa416b560ce07c78384f52d6fb76cddb5419b23882da36"`
Nov 17 21:57:36.325 INFO running `"docker" "rm" "-f" "96f56bf9e79e451f96fa416b560ce07c78384f52d6fb76cddb5419b23882da36"`
Nov 17 21:57:36.799 INFO [stdout] 96f56bf9e79e451f96fa416b560ce07c78384f52d6fb76cddb5419b23882da36