Nov 17 07:38:26.979 INFO testing brettcannon/flatten_filenames against master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c for pr-55982 Nov 17 07:38:26.980 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-6/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-6/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 07:38:27.332 INFO [stdout] 49d8c48f499b0e5ce5456d648b8080be6e1d1b1c2b81b254eacdc64457df8ec2 Nov 17 07:38:27.338 INFO running `"docker" "start" "-a" "49d8c48f499b0e5ce5456d648b8080be6e1d1b1c2b81b254eacdc64457df8ec2"` Nov 17 07:38:27.911 INFO [stderr] usermod: no changes Nov 17 07:38:27.999 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 17 07:38:27.999 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 17 07:38:27.999 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 17 07:38:27.999 INFO [stderr] files will be included as a binary target: Nov 17 07:38:27.999 INFO [stderr] Nov 17 07:38:27.999 INFO [stderr] * /source/src/main.rs Nov 17 07:38:27.999 INFO [stderr] Nov 17 07:38:27.999 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 17 07:38:27.999 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 17 07:38:27.999 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 17 07:38:27.999 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 17 07:38:27.999 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 17 07:38:27.999 INFO [stderr] Nov 17 07:38:27.999 INFO [stderr] For more information on this warning you can consult Nov 17 07:38:27.999 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 17 07:38:27.999 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `flatten-filenames`, Nov 17 07:38:27.999 INFO [stderr] please set bin.path in Cargo.toml Nov 17 07:38:28.027 INFO [stderr] Compiling flatten_filenames v0.1.0 (/source) Nov 17 07:38:28.734 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.79s Nov 17 07:38:28.736 INFO [stderr] su: No module specific data is present Nov 17 07:38:29.047 INFO running `"docker" "inspect" "49d8c48f499b0e5ce5456d648b8080be6e1d1b1c2b81b254eacdc64457df8ec2"` Nov 17 07:38:29.100 INFO running `"docker" "rm" "-f" "49d8c48f499b0e5ce5456d648b8080be6e1d1b1c2b81b254eacdc64457df8ec2"` Nov 17 07:38:29.177 INFO [stdout] 49d8c48f499b0e5ce5456d648b8080be6e1d1b1c2b81b254eacdc64457df8ec2 Nov 17 07:38:29.181 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-6/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-6/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 07:38:29.433 INFO [stdout] 74a77ecd553e38c18b97e7476e2f9a57b037386a630613d37cd7caac82837f31 Nov 17 07:38:29.437 INFO running `"docker" "start" "-a" "74a77ecd553e38c18b97e7476e2f9a57b037386a630613d37cd7caac82837f31"` Nov 17 07:38:29.880 INFO [stderr] usermod: no changes Nov 17 07:38:29.919 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 17 07:38:29.919 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 17 07:38:29.919 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 17 07:38:29.919 INFO [stderr] files will be included as a binary target: Nov 17 07:38:29.919 INFO [stderr] Nov 17 07:38:29.919 INFO [stderr] * /source/src/main.rs Nov 17 07:38:29.919 INFO [stderr] Nov 17 07:38:29.919 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 17 07:38:29.919 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 17 07:38:29.919 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 17 07:38:29.919 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 17 07:38:29.919 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 17 07:38:29.919 INFO [stderr] Nov 17 07:38:29.919 INFO [stderr] For more information on this warning you can consult Nov 17 07:38:29.919 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 17 07:38:29.919 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `flatten-filenames`, Nov 17 07:38:29.919 INFO [stderr] please set bin.path in Cargo.toml Nov 17 07:38:29.922 INFO [stderr] Compiling tempdir v0.3.5 Nov 17 07:38:30.464 INFO [stderr] Compiling flatten_filenames v0.1.0 (/source) Nov 17 07:38:31.601 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 1.70s Nov 17 07:38:31.604 INFO [stderr] su: No module specific data is present Nov 17 07:38:31.872 INFO running `"docker" "inspect" "74a77ecd553e38c18b97e7476e2f9a57b037386a630613d37cd7caac82837f31"` Nov 17 07:38:32.002 INFO running `"docker" "rm" "-f" "74a77ecd553e38c18b97e7476e2f9a57b037386a630613d37cd7caac82837f31"` Nov 17 07:38:32.117 INFO [stdout] 74a77ecd553e38c18b97e7476e2f9a57b037386a630613d37cd7caac82837f31 Nov 17 07:38:32.119 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-6/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-6/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" "-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 07:38:32.294 INFO [stdout] 8611810b75fb81cc4ec821592db48a4be3585655c51a90c59f7a1613b9edeb79 Nov 17 07:38:32.296 INFO running `"docker" "start" "-a" "8611810b75fb81cc4ec821592db48a4be3585655c51a90c59f7a1613b9edeb79"` Nov 17 07:38:32.805 INFO [stderr] usermod: no changes Nov 17 07:38:32.834 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 17 07:38:32.834 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 17 07:38:32.834 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 17 07:38:32.834 INFO [stderr] files will be included as a binary target: Nov 17 07:38:32.834 INFO [stderr] Nov 17 07:38:32.834 INFO [stderr] * /source/src/main.rs Nov 17 07:38:32.834 INFO [stderr] Nov 17 07:38:32.834 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 17 07:38:32.834 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 17 07:38:32.834 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 17 07:38:32.834 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 17 07:38:32.834 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 17 07:38:32.834 INFO [stderr] Nov 17 07:38:32.834 INFO [stderr] For more information on this warning you can consult Nov 17 07:38:32.834 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 17 07:38:32.834 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `flatten-filenames`, Nov 17 07:38:32.834 INFO [stderr] please set bin.path in Cargo.toml Nov 17 07:38:32.839 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.01s Nov 17 07:38:32.840 INFO [stderr] Running /target/debug/deps/flatten_filenames-05ba3d73ea9e204a Nov 17 07:38:32.845 INFO [stdout] Nov 17 07:38:32.846 INFO [stdout] running 10 tests Nov 17 07:38:32.846 INFO [stdout] test test::should_traverse_directory ... ok Nov 17 07:38:32.846 INFO [stdout] test test::new_prefix_works ... ok Nov 17 07:38:32.846 INFO [stdout] test test::new_prefix_leading_dash_or_plus ... ok Nov 17 07:38:32.846 INFO [stdout] test test::new_prefix_empty_old_prefix ... ok Nov 17 07:38:32.848 INFO [stdout] test test::rename_skips_dot_files ... ok Nov 17 07:38:32.848 INFO [stdout] test test::should_traverse_not_dir ... ok Nov 17 07:38:32.851 INFO [stdout] test test::leading_char_for_filename ... ok Nov 17 07:38:32.851 INFO [stdout] test test::rename_works ... ok Nov 17 07:38:32.851 INFO [stdout] test test::should_traverse_not_leading_dot_or_underscore ... ok Nov 17 07:38:32.858 INFO [stdout] test test::flatten_works ... ok Nov 17 07:38:32.858 INFO [stdout] Nov 17 07:38:32.858 INFO [stdout] test result: ok. 10 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Nov 17 07:38:32.858 INFO [stdout] Nov 17 07:38:32.860 INFO [stderr] su: No module specific data is present Nov 17 07:38:33.125 INFO running `"docker" "inspect" "8611810b75fb81cc4ec821592db48a4be3585655c51a90c59f7a1613b9edeb79"` Nov 17 07:38:33.197 INFO running `"docker" "rm" "-f" "8611810b75fb81cc4ec821592db48a4be3585655c51a90c59f7a1613b9edeb79"` Nov 17 07:38:33.296 INFO [stdout] 8611810b75fb81cc4ec821592db48a4be3585655c51a90c59f7a1613b9edeb79