Dec 14 18:38:53.401 INFO testing ssh2-0.3.3 against master#bd47d6825bf4090517549d33cfef10d3300b4a75 for pr-56550
Dec 14 18:38:53.401 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-4/master#bd47d6825bf4090517549d33cfef10d3300b4a75:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-56550/master#bd47d6825bf4090517549d33cfef10d3300b4a75:/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 +bd47d6825bf4090517549d33cfef10d3300b4a75-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"`
Dec 14 18:38:53.846 INFO [stdout] 0adf11f539195e86b1b53e1a1466eb0f58d2e10b48f3ad7a17ff8b48f5552948
Dec 14 18:38:53.848 INFO running `"docker" "start" "-a" "0adf11f539195e86b1b53e1a1466eb0f58d2e10b48f3ad7a17ff8b48f5552948"`
Dec 14 18:38:54.903 INFO [stderr] usermod: no changes
Dec 14 18:38:54.947 INFO [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently
Dec 14 18:38:54.947 INFO [stderr] disables Cargo from automatically inferring other test targets.
Dec 14 18:38:54.948 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 14 18:38:54.948 INFO [stderr] files will be included as a test target:
Dec 14 18:38:54.948 INFO [stderr] 
Dec 14 18:38:54.948 INFO [stderr] * /source/tests/session.rs
Dec 14 18:38:54.948 INFO [stderr] * /source/tests/channel.rs
Dec 14 18:38:54.948 INFO [stderr] * /source/tests/knownhosts.rs
Dec 14 18:38:54.948 INFO [stderr] * /source/tests/sftp.rs
Dec 14 18:38:54.948 INFO [stderr] * /source/tests/agent.rs
Dec 14 18:38:54.948 INFO [stderr] 
Dec 14 18:38:54.948 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 14 18:38:54.948 INFO [stderr] ready to be compiled as a test target today. You can future-proof yourself
Dec 14 18:38:54.948 INFO [stderr] and disable this warning by adding `autotests = false` to your [package]
Dec 14 18:38:54.948 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 14 18:38:54.948 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 14 18:38:54.948 INFO [stderr] 
Dec 14 18:38:54.948 INFO [stderr] For more information on this warning you can consult
Dec 14 18:38:54.948 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 14 18:38:55.022 INFO [stderr]    Compiling libssh2-sys v0.2.11
Dec 14 18:39:00.603 INFO [stderr]    Compiling ssh2 v0.3.3 (/source)
Dec 14 18:39:02.446 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 7.51s
Dec 14 18:39:02.459 INFO [stderr] su: No module specific data is present
Dec 14 18:39:03.379 INFO running `"docker" "inspect" "0adf11f539195e86b1b53e1a1466eb0f58d2e10b48f3ad7a17ff8b48f5552948"`
Dec 14 18:39:03.743 INFO running `"docker" "rm" "-f" "0adf11f539195e86b1b53e1a1466eb0f58d2e10b48f3ad7a17ff8b48f5552948"`
Dec 14 18:39:04.064 INFO [stdout] 0adf11f539195e86b1b53e1a1466eb0f58d2e10b48f3ad7a17ff8b48f5552948
Dec 14 18:39:04.073 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-4/master#bd47d6825bf4090517549d33cfef10d3300b4a75:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-56550/master#bd47d6825bf4090517549d33cfef10d3300b4a75:/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 +bd47d6825bf4090517549d33cfef10d3300b4a75-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"`
Dec 14 18:39:04.457 INFO [stdout] 784507da3e1319315b7a3f4f21de2cebca5160f6d0d5cca51ca16c0099c8d358
Dec 14 18:39:04.464 INFO running `"docker" "start" "-a" "784507da3e1319315b7a3f4f21de2cebca5160f6d0d5cca51ca16c0099c8d358"`
Dec 14 18:39:05.619 INFO [stderr] usermod: no changes
Dec 14 18:39:05.679 INFO [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently
Dec 14 18:39:05.679 INFO [stderr] disables Cargo from automatically inferring other test targets.
Dec 14 18:39:05.679 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 14 18:39:05.679 INFO [stderr] files will be included as a test target:
Dec 14 18:39:05.679 INFO [stderr] 
Dec 14 18:39:05.679 INFO [stderr] * /source/tests/session.rs
Dec 14 18:39:05.679 INFO [stderr] * /source/tests/channel.rs
Dec 14 18:39:05.679 INFO [stderr] * /source/tests/knownhosts.rs
Dec 14 18:39:05.679 INFO [stderr] * /source/tests/sftp.rs
Dec 14 18:39:05.679 INFO [stderr] * /source/tests/agent.rs
Dec 14 18:39:05.679 INFO [stderr] 
Dec 14 18:39:05.679 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 14 18:39:05.679 INFO [stderr] ready to be compiled as a test target today. You can future-proof yourself
Dec 14 18:39:05.679 INFO [stderr] and disable this warning by adding `autotests = false` to your [package]
Dec 14 18:39:05.679 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 14 18:39:05.679 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 14 18:39:05.679 INFO [stderr] 
Dec 14 18:39:05.679 INFO [stderr] For more information on this warning you can consult
Dec 14 18:39:05.679 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 14 18:39:05.735 INFO [stderr]    Compiling ssh2 v0.3.3 (/source)
Dec 14 18:39:08.955 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 3.29s
Dec 14 18:39:08.955 INFO [stderr] su: No module specific data is present
Dec 14 18:39:09.694 INFO running `"docker" "inspect" "784507da3e1319315b7a3f4f21de2cebca5160f6d0d5cca51ca16c0099c8d358"`
Dec 14 18:39:10.005 INFO running `"docker" "rm" "-f" "784507da3e1319315b7a3f4f21de2cebca5160f6d0d5cca51ca16c0099c8d358"`
Dec 14 18:39:10.295 INFO [stdout] 784507da3e1319315b7a3f4f21de2cebca5160f6d0d5cca51ca16c0099c8d358