Dec 06 04:56:06.448 INFO testing brettcannon/flatten_filenames against master#906deae0790bd18681b937fe9a141a3c26cf1855 for pr-56514 Dec 06 04:56:06.448 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-7/master#906deae0790bd18681b937fe9a141a3c26cf1855:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/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 04:56:06.624 INFO [stdout] cb0fba4332e9fcf8bc7870d6935b48a98ca4650227c4d2afac993549b70eb17c Dec 06 04:56:06.629 INFO running `"docker" "start" "-a" "cb0fba4332e9fcf8bc7870d6935b48a98ca4650227c4d2afac993549b70eb17c"` Dec 06 04:56:07.209 INFO [stderr] usermod: no changes Dec 06 04:56:07.232 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 06 04:56:07.232 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 06 04:56:07.232 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 06 04:56:07.232 INFO [stderr] files will be included as a binary target: Dec 06 04:56:07.232 INFO [stderr] Dec 06 04:56:07.232 INFO [stderr] * /source/src/main.rs Dec 06 04:56:07.232 INFO [stderr] Dec 06 04:56:07.232 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 06 04:56:07.232 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 06 04:56:07.232 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 06 04:56:07.232 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 06 04:56:07.232 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 06 04:56:07.232 INFO [stderr] Dec 06 04:56:07.232 INFO [stderr] For more information on this warning you can consult Dec 06 04:56:07.232 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 06 04:56:07.232 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `flatten-filenames`, Dec 06 04:56:07.232 INFO [stderr] please set bin.path in Cargo.toml Dec 06 04:56:07.236 INFO [stderr] Compiling flatten_filenames v0.1.0 (/source) Dec 06 04:56:07.907 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.68s Dec 06 04:56:07.909 INFO [stderr] su: No module specific data is present Dec 06 04:56:08.162 INFO running `"docker" "inspect" "cb0fba4332e9fcf8bc7870d6935b48a98ca4650227c4d2afac993549b70eb17c"` Dec 06 04:56:08.304 INFO running `"docker" "rm" "-f" "cb0fba4332e9fcf8bc7870d6935b48a98ca4650227c4d2afac993549b70eb17c"` Dec 06 04:56:08.424 INFO [stdout] cb0fba4332e9fcf8bc7870d6935b48a98ca4650227c4d2afac993549b70eb17c Dec 06 04:56:08.430 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-7/master#906deae0790bd18681b937fe9a141a3c26cf1855:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/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 04:56:08.631 INFO [stdout] 51f371c3eb5ecc00149c438d67545487c26368cace8bd7fe2dcf17568578847e Dec 06 04:56:08.634 INFO running `"docker" "start" "-a" "51f371c3eb5ecc00149c438d67545487c26368cace8bd7fe2dcf17568578847e"` Dec 06 04:56:09.001 INFO [stderr] usermod: no changes Dec 06 04:56:09.032 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 06 04:56:09.032 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 06 04:56:09.032 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 06 04:56:09.032 INFO [stderr] files will be included as a binary target: Dec 06 04:56:09.032 INFO [stderr] Dec 06 04:56:09.032 INFO [stderr] * /source/src/main.rs Dec 06 04:56:09.032 INFO [stderr] Dec 06 04:56:09.032 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 06 04:56:09.032 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 06 04:56:09.032 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 06 04:56:09.032 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 06 04:56:09.032 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 06 04:56:09.032 INFO [stderr] Dec 06 04:56:09.032 INFO [stderr] For more information on this warning you can consult Dec 06 04:56:09.032 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 06 04:56:09.032 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `flatten-filenames`, Dec 06 04:56:09.032 INFO [stderr] please set bin.path in Cargo.toml Dec 06 04:56:09.034 INFO [stderr] Compiling rand v0.3.14 Dec 06 04:56:10.480 INFO [stderr] Compiling tempdir v0.3.5 Dec 06 04:56:10.984 INFO [stderr] Compiling flatten_filenames v0.1.0 (/source) Dec 06 04:56:12.215 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 3.20s Dec 06 04:56:12.218 INFO [stderr] su: No module specific data is present Dec 06 04:56:12.677 INFO running `"docker" "inspect" "51f371c3eb5ecc00149c438d67545487c26368cace8bd7fe2dcf17568578847e"` Dec 06 04:56:12.766 INFO running `"docker" "rm" "-f" "51f371c3eb5ecc00149c438d67545487c26368cace8bd7fe2dcf17568578847e"` Dec 06 04:56:12.868 INFO [stdout] 51f371c3eb5ecc00149c438d67545487c26368cace8bd7fe2dcf17568578847e Dec 06 04:56:12.870 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-7/master#906deae0790bd18681b937fe9a141a3c26cf1855:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/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 04:56:13.041 INFO [stdout] 313690e98437b1fa406c5f68a80138b3633028d17a1b293a4447d1bf5d1f8aaf Dec 06 04:56:13.044 INFO running `"docker" "start" "-a" "313690e98437b1fa406c5f68a80138b3633028d17a1b293a4447d1bf5d1f8aaf"` Dec 06 04:56:13.460 INFO [stderr] usermod: no changes Dec 06 04:56:13.492 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 06 04:56:13.492 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 06 04:56:13.492 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 06 04:56:13.492 INFO [stderr] files will be included as a binary target: Dec 06 04:56:13.492 INFO [stderr] Dec 06 04:56:13.492 INFO [stderr] * /source/src/main.rs Dec 06 04:56:13.492 INFO [stderr] Dec 06 04:56:13.492 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 06 04:56:13.492 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 06 04:56:13.492 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 06 04:56:13.492 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 06 04:56:13.492 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 06 04:56:13.492 INFO [stderr] Dec 06 04:56:13.492 INFO [stderr] For more information on this warning you can consult Dec 06 04:56:13.492 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 06 04:56:13.492 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `flatten-filenames`, Dec 06 04:56:13.492 INFO [stderr] please set bin.path in Cargo.toml Dec 06 04:56:13.492 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.01s Dec 06 04:56:13.493 INFO [stderr] Running /target/debug/deps/flatten_filenames-482846d8a6a623dc Dec 06 04:56:13.508 INFO [stdout] Dec 06 04:56:13.508 INFO [stdout] running 10 tests Dec 06 04:56:13.516 INFO [stdout] test test::new_prefix_empty_old_prefix ... ok Dec 06 04:56:13.516 INFO [stdout] test test::leading_char_for_filename ... ok Dec 06 04:56:13.516 INFO [stdout] test test::new_prefix_leading_dash_or_plus ... ok Dec 06 04:56:13.516 INFO [stdout] test test::new_prefix_works ... ok Dec 06 04:56:13.517 INFO [stdout] test test::should_traverse_not_leading_dot_or_underscore ... ok Dec 06 04:56:13.518 INFO [stdout] test test::should_traverse_directory ... ok Dec 06 04:56:13.523 INFO [stdout] test test::rename_skips_dot_files ... ok Dec 06 04:56:13.524 INFO [stdout] test test::rename_works ... ok Dec 06 04:56:13.524 INFO [stdout] test test::should_traverse_not_dir ... ok Dec 06 04:56:13.525 INFO [stdout] test test::flatten_works ... ok Dec 06 04:56:13.525 INFO [stdout] Dec 06 04:56:13.525 INFO [stdout] test result: ok. 10 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 06 04:56:13.525 INFO [stdout] Dec 06 04:56:13.528 INFO [stderr] su: No module specific data is present Dec 06 04:56:14.046 INFO running `"docker" "inspect" "313690e98437b1fa406c5f68a80138b3633028d17a1b293a4447d1bf5d1f8aaf"` Dec 06 04:56:14.185 INFO running `"docker" "rm" "-f" "313690e98437b1fa406c5f68a80138b3633028d17a1b293a4447d1bf5d1f8aaf"` Dec 06 04:56:14.259 INFO [stdout] 313690e98437b1fa406c5f68a80138b3633028d17a1b293a4447d1bf5d1f8aaf