Nov 18 12:50:59.784 INFO testing glusterchangelog-0.1.2 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982
Nov 18 12:50:59.786 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-2/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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 18 12:51:00.425 INFO [stdout] 0a75a910398f7fd806c11579eeb92cba9a251d1e13e8a168bb01fd0f6392d707
Nov 18 12:51:00.428 INFO running `"docker" "start" "-a" "0a75a910398f7fd806c11579eeb92cba9a251d1e13e8a168bb01fd0f6392d707"`
Nov 18 12:51:01.343 INFO [stderr] usermod: no changes
Nov 18 12:51:01.377 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:51:01.378 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:51:01.378 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:51:01.378 INFO [stderr] files will be included as a binary target:
Nov 18 12:51:01.379 INFO [stderr] 
Nov 18 12:51:01.379 INFO [stderr] * /source/src/main.rs
Nov 18 12:51:01.379 INFO [stderr] 
Nov 18 12:51:01.379 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:51:01.380 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:51:01.380 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:51:01.380 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:51:01.381 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:51:01.381 INFO [stderr] 
Nov 18 12:51:01.381 INFO [stderr] For more information on this warning you can consult
Nov 18 12:51:01.382 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:51:01.382 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `glusterchangelogparser`,
Nov 18 12:51:01.382 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:51:01.382 INFO [stderr]    Compiling glusterchangelog v0.1.2 (/source)
Nov 18 12:51:03.463 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.09s
Nov 18 12:51:03.463 INFO [stderr] su: No module specific data is present
Nov 18 12:51:04.505 INFO running `"docker" "inspect" "0a75a910398f7fd806c11579eeb92cba9a251d1e13e8a168bb01fd0f6392d707"`
Nov 18 12:51:04.845 INFO running `"docker" "rm" "-f" "0a75a910398f7fd806c11579eeb92cba9a251d1e13e8a168bb01fd0f6392d707"`
Nov 18 12:51:05.200 INFO [stdout] 0a75a910398f7fd806c11579eeb92cba9a251d1e13e8a168bb01fd0f6392d707
Nov 18 12:51:05.209 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-2/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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 18 12:51:05.672 INFO [stdout] 61044d6d5f706036684b29b0f20197cf586570b7b5457aba3e03306a69ef2f0d
Nov 18 12:51:05.677 INFO running `"docker" "start" "-a" "61044d6d5f706036684b29b0f20197cf586570b7b5457aba3e03306a69ef2f0d"`
Nov 18 12:51:07.777 INFO [stderr] usermod: no changes
Nov 18 12:51:07.863 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:51:07.863 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:51:07.863 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:51:07.863 INFO [stderr] files will be included as a binary target:
Nov 18 12:51:07.863 INFO [stderr] 
Nov 18 12:51:07.863 INFO [stderr] * /source/src/main.rs
Nov 18 12:51:07.863 INFO [stderr] 
Nov 18 12:51:07.863 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:51:07.863 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:51:07.863 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:51:07.863 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:51:07.863 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:51:07.863 INFO [stderr] 
Nov 18 12:51:07.863 INFO [stderr] For more information on this warning you can consult
Nov 18 12:51:07.863 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:51:07.863 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `glusterchangelogparser`,
Nov 18 12:51:07.863 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:51:07.879 INFO [stderr]    Compiling glusterchangelog v0.1.2 (/source)
Nov 18 12:51:10.359 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.54s
Nov 18 12:51:10.363 INFO [stderr] su: No module specific data is present
Nov 18 12:51:11.235 INFO running `"docker" "inspect" "61044d6d5f706036684b29b0f20197cf586570b7b5457aba3e03306a69ef2f0d"`
Nov 18 12:51:11.505 INFO running `"docker" "rm" "-f" "61044d6d5f706036684b29b0f20197cf586570b7b5457aba3e03306a69ef2f0d"`
Nov 18 12:51:11.767 INFO [stdout] 61044d6d5f706036684b29b0f20197cf586570b7b5457aba3e03306a69ef2f0d
Nov 18 12:51:11.774 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-2/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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" "-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 18 12:51:12.268 INFO [stdout] a73d991446a688a06e4778b60f030c3bf757e985be6a658cc3d1e51ca3b9d231
Nov 18 12:51:12.271 INFO running `"docker" "start" "-a" "a73d991446a688a06e4778b60f030c3bf757e985be6a658cc3d1e51ca3b9d231"`
Nov 18 12:51:13.670 INFO [stderr] usermod: no changes
Nov 18 12:51:13.711 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:51:13.711 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:51:13.711 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:51:13.711 INFO [stderr] files will be included as a binary target:
Nov 18 12:51:13.711 INFO [stderr] 
Nov 18 12:51:13.711 INFO [stderr] * /source/src/main.rs
Nov 18 12:51:13.711 INFO [stderr] 
Nov 18 12:51:13.711 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:51:13.711 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:51:13.711 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:51:13.711 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:51:13.711 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:51:13.711 INFO [stderr] 
Nov 18 12:51:13.711 INFO [stderr] For more information on this warning you can consult
Nov 18 12:51:13.711 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:51:13.711 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `glusterchangelogparser`,
Nov 18 12:51:13.711 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:51:13.711 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.01s
Nov 18 12:51:13.719 INFO [stderr]      Running /target/debug/deps/glusterchangelog-d6132d09183f01d7
Nov 18 12:51:13.719 INFO [stdout] 
Nov 18 12:51:13.719 INFO [stderr]      Running /target/debug/deps/glusterchangelogparser-5b04e278daf20546
Nov 18 12:51:13.719 INFO [stdout] running 0 tests
Nov 18 12:51:13.719 INFO [stdout] 
Nov 18 12:51:13.719 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 12:51:13.719 INFO [stdout] 
Nov 18 12:51:13.727 INFO [stdout] 
Nov 18 12:51:13.727 INFO [stderr]    Doc-tests glusterchangelog
Nov 18 12:51:13.727 INFO [stdout] running 0 tests
Nov 18 12:51:13.727 INFO [stdout] 
Nov 18 12:51:13.727 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 12:51:13.727 INFO [stdout] 
Nov 18 12:51:14.543 INFO [stdout] 
Nov 18 12:51:14.543 INFO [stdout] running 0 tests
Nov 18 12:51:14.543 INFO [stdout] 
Nov 18 12:51:14.543 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 12:51:14.543 INFO [stdout] 
Nov 18 12:51:14.552 INFO [stderr] su: No module specific data is present
Nov 18 12:51:15.362 INFO running `"docker" "inspect" "a73d991446a688a06e4778b60f030c3bf757e985be6a658cc3d1e51ca3b9d231"`
Nov 18 12:51:15.619 INFO running `"docker" "rm" "-f" "a73d991446a688a06e4778b60f030c3bf757e985be6a658cc3d1e51ca3b9d231"`
Nov 18 12:51:15.823 INFO [stdout] a73d991446a688a06e4778b60f030c3bf757e985be6a658cc3d1e51ca3b9d231