Dec 06 05:27:31.685 INFO testing bionikspoon/minigrep against master#906deae0790bd18681b937fe9a141a3c26cf1855 for pr-56514
Dec 06 05:27:31.686 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-4/master#906deae0790bd18681b937fe9a141a3c26cf1855:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-56514/master#906deae0790bd18681b937fe9a141a3c26cf1855:/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 +906deae0790bd18681b937fe9a141a3c26cf1855-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 06 05:27:32.109 INFO [stdout] 5a896816ca8f65cd34cbae9dc87fcafb3bbbe2e18691b8c9891a2b28bc621932
Dec 06 05:27:32.111 INFO running `"docker" "start" "-a" "5a896816ca8f65cd34cbae9dc87fcafb3bbbe2e18691b8c9891a2b28bc621932"`
Dec 06 05:27:33.327 INFO [stderr] usermod: no changes
Dec 06 05:27:33.364 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 06 05:27:33.364 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 06 05:27:33.364 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 06 05:27:33.364 INFO [stderr] files will be included as a binary target:
Dec 06 05:27:33.364 INFO [stderr] 
Dec 06 05:27:33.364 INFO [stderr] * /source/src/main.rs
Dec 06 05:27:33.364 INFO [stderr] 
Dec 06 05:27:33.364 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 06 05:27:33.364 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 06 05:27:33.364 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 06 05:27:33.364 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 06 05:27:33.364 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 06 05:27:33.364 INFO [stderr] 
Dec 06 05:27:33.364 INFO [stderr] For more information on this warning you can consult
Dec 06 05:27:33.364 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 06 05:27:33.364 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `minigrep`,
Dec 06 05:27:33.364 INFO [stderr] please set bin.path in Cargo.toml
Dec 06 05:27:33.372 INFO [stderr]    Compiling minigrep_lib v0.1.0 (/source)
Dec 06 05:27:34.940 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.59s
Dec 06 05:27:34.968 INFO [stderr] su: No module specific data is present
Dec 06 05:27:35.537 INFO running `"docker" "inspect" "5a896816ca8f65cd34cbae9dc87fcafb3bbbe2e18691b8c9891a2b28bc621932"`
Dec 06 05:27:35.802 INFO running `"docker" "rm" "-f" "5a896816ca8f65cd34cbae9dc87fcafb3bbbe2e18691b8c9891a2b28bc621932"`
Dec 06 05:27:36.112 INFO [stdout] 5a896816ca8f65cd34cbae9dc87fcafb3bbbe2e18691b8c9891a2b28bc621932
Dec 06 05:27:36.114 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-4/master#906deae0790bd18681b937fe9a141a3c26cf1855:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-56514/master#906deae0790bd18681b937fe9a141a3c26cf1855:/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 +906deae0790bd18681b937fe9a141a3c26cf1855-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 06 05:27:36.514 INFO [stdout] 34cc1405130d0c067ae8a4f1735bf05815ca30c242f7931456c9e9ac9c4337b6
Dec 06 05:27:36.518 INFO running `"docker" "start" "-a" "34cc1405130d0c067ae8a4f1735bf05815ca30c242f7931456c9e9ac9c4337b6"`
Dec 06 05:27:37.140 INFO [stderr] usermod: no changes
Dec 06 05:27:37.184 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 06 05:27:37.184 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 06 05:27:37.184 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 06 05:27:37.184 INFO [stderr] files will be included as a binary target:
Dec 06 05:27:37.184 INFO [stderr] 
Dec 06 05:27:37.184 INFO [stderr] * /source/src/main.rs
Dec 06 05:27:37.184 INFO [stderr] 
Dec 06 05:27:37.184 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 06 05:27:37.184 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 06 05:27:37.184 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 06 05:27:37.184 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 06 05:27:37.184 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 06 05:27:37.185 INFO [stderr] 
Dec 06 05:27:37.185 INFO [stderr] For more information on this warning you can consult
Dec 06 05:27:37.185 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 06 05:27:37.185 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `minigrep`,
Dec 06 05:27:37.185 INFO [stderr] please set bin.path in Cargo.toml
Dec 06 05:27:37.188 INFO [stderr]    Compiling minigrep_lib v0.1.0 (/source)
Dec 06 05:27:38.124 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.95s
Dec 06 05:27:38.132 INFO [stderr] su: No module specific data is present
Dec 06 05:27:38.555 INFO running `"docker" "inspect" "34cc1405130d0c067ae8a4f1735bf05815ca30c242f7931456c9e9ac9c4337b6"`
Dec 06 05:27:38.693 INFO running `"docker" "rm" "-f" "34cc1405130d0c067ae8a4f1735bf05815ca30c242f7931456c9e9ac9c4337b6"`
Dec 06 05:27:38.800 INFO [stdout] 34cc1405130d0c067ae8a4f1735bf05815ca30c242f7931456c9e9ac9c4337b6
Dec 06 05:27:38.802 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-4/master#906deae0790bd18681b937fe9a141a3c26cf1855:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-56514/master#906deae0790bd18681b937fe9a141a3c26cf1855:/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 +906deae0790bd18681b937fe9a141a3c26cf1855-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"`
Dec 06 05:27:38.960 INFO [stdout] c1d0cc34e65c99b7c157cddbed2d0ee0785e66feb21498696841c41103afbdeb
Dec 06 05:27:38.962 INFO running `"docker" "start" "-a" "c1d0cc34e65c99b7c157cddbed2d0ee0785e66feb21498696841c41103afbdeb"`
Dec 06 05:27:39.426 INFO [stderr] usermod: no changes
Dec 06 05:27:39.446 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 06 05:27:39.446 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 06 05:27:39.446 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 06 05:27:39.446 INFO [stderr] files will be included as a binary target:
Dec 06 05:27:39.446 INFO [stderr] 
Dec 06 05:27:39.446 INFO [stderr] * /source/src/main.rs
Dec 06 05:27:39.446 INFO [stderr] 
Dec 06 05:27:39.446 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 06 05:27:39.446 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 06 05:27:39.446 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 06 05:27:39.446 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 06 05:27:39.446 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 06 05:27:39.446 INFO [stderr] 
Dec 06 05:27:39.446 INFO [stderr] For more information on this warning you can consult
Dec 06 05:27:39.446 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 06 05:27:39.446 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `minigrep`,
Dec 06 05:27:39.447 INFO [stderr] please set bin.path in Cargo.toml
Dec 06 05:27:39.448 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.01s
Dec 06 05:27:39.448 INFO [stderr]      Running /target/debug/deps/minigrep_lib-70ff47fddfd5cfd4
Dec 06 05:27:39.449 INFO [stdout] 
Dec 06 05:27:39.449 INFO [stdout] running 2 tests
Dec 06 05:27:39.449 INFO [stdout] test tests::search_has_one_result ... ok
Dec 06 05:27:39.450 INFO [stdout] test tests::case_insensitive ... ok
Dec 06 05:27:39.450 INFO [stdout] 
Dec 06 05:27:39.450 INFO [stdout] test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 06 05:27:39.450 INFO [stdout] 
Dec 06 05:27:39.450 INFO [stderr]      Running /target/debug/deps/minigrep-f6926159ae621e39
Dec 06 05:27:39.451 INFO [stdout] 
Dec 06 05:27:39.451 INFO [stdout] running 0 tests
Dec 06 05:27:39.451 INFO [stdout] 
Dec 06 05:27:39.451 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 06 05:27:39.451 INFO [stdout] 
Dec 06 05:27:39.451 INFO [stderr]    Doc-tests minigrep_lib
Dec 06 05:27:39.978 INFO [stdout] 
Dec 06 05:27:39.978 INFO [stdout] running 0 tests
Dec 06 05:27:39.978 INFO [stdout] 
Dec 06 05:27:39.978 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 06 05:27:39.978 INFO [stdout] 
Dec 06 05:27:39.981 INFO [stderr] su: No module specific data is present
Dec 06 05:27:40.550 INFO running `"docker" "inspect" "c1d0cc34e65c99b7c157cddbed2d0ee0785e66feb21498696841c41103afbdeb"`
Dec 06 05:27:40.702 INFO running `"docker" "rm" "-f" "c1d0cc34e65c99b7c157cddbed2d0ee0785e66feb21498696841c41103afbdeb"`
Dec 06 05:27:40.828 INFO [stdout] c1d0cc34e65c99b7c157cddbed2d0ee0785e66feb21498696841c41103afbdeb