Dec 14 00:48:30.449 INFO testing brettcannon/flatten_filenames against try#aa49d8ef14939ddec0e34b346b60174a5673d48f for pr-56550 Dec 14 00:48:30.449 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-0/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/pr-56550/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/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 +aa49d8ef14939ddec0e34b346b60174a5673d48f-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 00:48:30.883 INFO [stdout] 636da1c4a04b5a8b22585a6eeeace4ecd7c9fa867a3cf9bbc91f192776abad42 Dec 14 00:48:30.885 INFO running `"docker" "start" "-a" "636da1c4a04b5a8b22585a6eeeace4ecd7c9fa867a3cf9bbc91f192776abad42"` Dec 14 00:48:32.754 INFO [stderr] usermod: no changes Dec 14 00:48:32.818 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 14 00:48:32.818 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 14 00:48:32.818 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 14 00:48:32.818 INFO [stderr] files will be included as a binary target: Dec 14 00:48:32.818 INFO [stderr] Dec 14 00:48:32.818 INFO [stderr] * /source/src/main.rs Dec 14 00:48:32.818 INFO [stderr] Dec 14 00:48:32.818 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 14 00:48:32.818 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 14 00:48:32.818 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 14 00:48:32.818 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 14 00:48:32.818 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 14 00:48:32.818 INFO [stderr] Dec 14 00:48:32.818 INFO [stderr] For more information on this warning you can consult Dec 14 00:48:32.818 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 14 00:48:32.818 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `flatten-filenames`, Dec 14 00:48:32.818 INFO [stderr] please set bin.path in Cargo.toml Dec 14 00:48:32.827 INFO [stderr] Compiling flatten_filenames v0.1.0 (/source) Dec 14 00:48:34.023 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 1.23s Dec 14 00:48:34.026 INFO [stderr] su: No module specific data is present Dec 14 00:48:34.852 INFO running `"docker" "inspect" "636da1c4a04b5a8b22585a6eeeace4ecd7c9fa867a3cf9bbc91f192776abad42"` Dec 14 00:48:35.098 INFO running `"docker" "rm" "-f" "636da1c4a04b5a8b22585a6eeeace4ecd7c9fa867a3cf9bbc91f192776abad42"` Dec 14 00:48:35.261 INFO [stdout] 636da1c4a04b5a8b22585a6eeeace4ecd7c9fa867a3cf9bbc91f192776abad42 Dec 14 00:48:35.268 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-0/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/pr-56550/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/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 +aa49d8ef14939ddec0e34b346b60174a5673d48f-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 00:48:35.477 INFO [stdout] 5e89a4d6c5d68867ab4dbc17140e4042ef0568191c6b2b87f34c916396c35f3f Dec 14 00:48:35.483 INFO running `"docker" "start" "-a" "5e89a4d6c5d68867ab4dbc17140e4042ef0568191c6b2b87f34c916396c35f3f"` Dec 14 00:48:36.316 INFO [stderr] usermod: no changes Dec 14 00:48:36.387 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 14 00:48:36.387 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 14 00:48:36.387 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 14 00:48:36.387 INFO [stderr] files will be included as a binary target: Dec 14 00:48:36.387 INFO [stderr] Dec 14 00:48:36.387 INFO [stderr] * /source/src/main.rs Dec 14 00:48:36.387 INFO [stderr] Dec 14 00:48:36.387 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 14 00:48:36.387 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 14 00:48:36.387 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 14 00:48:36.387 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 14 00:48:36.387 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 14 00:48:36.387 INFO [stderr] Dec 14 00:48:36.387 INFO [stderr] For more information on this warning you can consult Dec 14 00:48:36.387 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 14 00:48:36.387 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `flatten-filenames`, Dec 14 00:48:36.387 INFO [stderr] please set bin.path in Cargo.toml Dec 14 00:48:36.406 INFO [stderr] Compiling tempdir v0.3.5 Dec 14 00:48:37.031 INFO [stderr] Compiling flatten_filenames v0.1.0 (/source) Dec 14 00:48:38.115 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 1.74s Dec 14 00:48:38.115 INFO [stderr] su: No module specific data is present Dec 14 00:48:38.401 INFO running `"docker" "inspect" "5e89a4d6c5d68867ab4dbc17140e4042ef0568191c6b2b87f34c916396c35f3f"` Dec 14 00:48:38.477 INFO running `"docker" "rm" "-f" "5e89a4d6c5d68867ab4dbc17140e4042ef0568191c6b2b87f34c916396c35f3f"` Dec 14 00:48:38.576 INFO [stdout] 5e89a4d6c5d68867ab4dbc17140e4042ef0568191c6b2b87f34c916396c35f3f Dec 14 00:48:38.581 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-0/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/pr-56550/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/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 +aa49d8ef14939ddec0e34b346b60174a5673d48f-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 14 00:48:38.779 INFO [stdout] ce74e7d14b0e1e04be58c6250c7936200f8a3232ea17ed37315cbf11b7bf6712 Dec 14 00:48:38.781 INFO running `"docker" "start" "-a" "ce74e7d14b0e1e04be58c6250c7936200f8a3232ea17ed37315cbf11b7bf6712"` Dec 14 00:48:39.512 INFO [stderr] usermod: no changes Dec 14 00:48:39.555 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 14 00:48:39.555 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 14 00:48:39.555 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 14 00:48:39.555 INFO [stderr] files will be included as a binary target: Dec 14 00:48:39.555 INFO [stderr] Dec 14 00:48:39.555 INFO [stderr] * /source/src/main.rs Dec 14 00:48:39.555 INFO [stderr] Dec 14 00:48:39.555 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 14 00:48:39.555 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 14 00:48:39.555 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 14 00:48:39.555 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 14 00:48:39.555 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 14 00:48:39.555 INFO [stderr] Dec 14 00:48:39.555 INFO [stderr] For more information on this warning you can consult Dec 14 00:48:39.555 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 14 00:48:39.555 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `flatten-filenames`, Dec 14 00:48:39.555 INFO [stderr] please set bin.path in Cargo.toml Dec 14 00:48:39.560 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.02s Dec 14 00:48:39.563 INFO [stderr] Running /target/debug/deps/flatten_filenames-416eeb8800c89c42 Dec 14 00:48:39.576 INFO [stdout] Dec 14 00:48:39.576 INFO [stdout] running 10 tests Dec 14 00:48:39.577 INFO [stdout] test test::new_prefix_leading_dash_or_plus ... ok Dec 14 00:48:39.578 INFO [stdout] test test::new_prefix_works ... ok Dec 14 00:48:39.579 INFO [stdout] test test::leading_char_for_filename ... ok Dec 14 00:48:39.579 INFO [stdout] test test::new_prefix_empty_old_prefix ... ok Dec 14 00:48:39.580 INFO [stdout] test test::should_traverse_directory ... ok Dec 14 00:48:39.581 INFO [stdout] test test::rename_works ... ok Dec 14 00:48:39.581 INFO [stdout] test test::rename_skips_dot_files ... ok Dec 14 00:48:39.581 INFO [stdout] test test::should_traverse_not_leading_dot_or_underscore ... ok Dec 14 00:48:39.581 INFO [stdout] test test::should_traverse_not_dir ... ok Dec 14 00:48:39.596 INFO [stdout] test test::flatten_works ... ok Dec 14 00:48:39.596 INFO [stderr] su: No module specific data is present Dec 14 00:48:39.596 INFO [stdout] Dec 14 00:48:39.596 INFO [stdout] test result: ok. 10 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 14 00:48:39.596 INFO [stdout] Dec 14 00:48:40.016 INFO running `"docker" "inspect" "ce74e7d14b0e1e04be58c6250c7936200f8a3232ea17ed37315cbf11b7bf6712"` Dec 14 00:48:40.108 INFO running `"docker" "rm" "-f" "ce74e7d14b0e1e04be58c6250c7936200f8a3232ea17ed37315cbf11b7bf6712"` Dec 14 00:48:40.164 INFO [stdout] ce74e7d14b0e1e04be58c6250c7936200f8a3232ea17ed37315cbf11b7bf6712