Dec 06 04:55:58.256 INFO testing brettcannon/flatten_filenames against try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468 for pr-56514 Dec 06 04:55:58.256 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-7/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/pr-56514/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/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 +6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468-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:55:58.435 INFO [stdout] 4640124b103e12fe7dcb0949b430219ac589b635186d1a8b3ca6183d833f7738 Dec 06 04:55:58.437 INFO running `"docker" "start" "-a" "4640124b103e12fe7dcb0949b430219ac589b635186d1a8b3ca6183d833f7738"` Dec 06 04:55:58.832 INFO [stderr] usermod: no changes Dec 06 04:55:58.853 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 06 04:55:58.853 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 06 04:55:58.853 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 06 04:55:58.853 INFO [stderr] files will be included as a binary target: Dec 06 04:55:58.853 INFO [stderr] Dec 06 04:55:58.853 INFO [stderr] * /source/src/main.rs Dec 06 04:55:58.853 INFO [stderr] Dec 06 04:55:58.853 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 06 04:55:58.853 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 06 04:55:58.853 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 06 04:55:58.853 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 06 04:55:58.853 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 06 04:55:58.853 INFO [stderr] Dec 06 04:55:58.853 INFO [stderr] For more information on this warning you can consult Dec 06 04:55:58.853 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 06 04:55:58.853 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `flatten-filenames`, Dec 06 04:55:58.853 INFO [stderr] please set bin.path in Cargo.toml Dec 06 04:55:58.856 INFO [stderr] Compiling flatten_filenames v0.1.0 (/source) Dec 06 04:55:59.828 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.98s Dec 06 04:55:59.831 INFO [stderr] su: No module specific data is present Dec 06 04:56:00.485 INFO running `"docker" "inspect" "4640124b103e12fe7dcb0949b430219ac589b635186d1a8b3ca6183d833f7738"` Dec 06 04:56:00.693 INFO running `"docker" "rm" "-f" "4640124b103e12fe7dcb0949b430219ac589b635186d1a8b3ca6183d833f7738"` Dec 06 04:56:00.984 INFO [stdout] 4640124b103e12fe7dcb0949b430219ac589b635186d1a8b3ca6183d833f7738 Dec 06 04:56:00.992 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-7/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/pr-56514/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/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 +6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468-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:01.328 INFO [stdout] 807f12b6fbafbd0b5ab69abfbc1f7204a79171585477f12733fa673c00cbad77 Dec 06 04:56:01.336 INFO running `"docker" "start" "-a" "807f12b6fbafbd0b5ab69abfbc1f7204a79171585477f12733fa673c00cbad77"` Dec 06 04:56:02.287 INFO [stderr] usermod: no changes Dec 06 04:56:02.313 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 06 04:56:02.314 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 06 04:56:02.314 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 06 04:56:02.314 INFO [stderr] files will be included as a binary target: Dec 06 04:56:02.314 INFO [stderr] Dec 06 04:56:02.314 INFO [stderr] * /source/src/main.rs Dec 06 04:56:02.314 INFO [stderr] Dec 06 04:56:02.314 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 06 04:56:02.314 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 06 04:56:02.314 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 06 04:56:02.314 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 06 04:56:02.314 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 06 04:56:02.314 INFO [stderr] Dec 06 04:56:02.314 INFO [stderr] For more information on this warning you can consult Dec 06 04:56:02.314 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 06 04:56:02.314 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `flatten-filenames`, Dec 06 04:56:02.314 INFO [stderr] please set bin.path in Cargo.toml Dec 06 04:56:02.321 INFO [stderr] Compiling tempdir v0.3.5 Dec 06 04:56:02.836 INFO [stderr] Compiling flatten_filenames v0.1.0 (/source) Dec 06 04:56:04.007 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 1.70s Dec 06 04:56:04.010 INFO [stderr] su: No module specific data is present Dec 06 04:56:04.690 INFO running `"docker" "inspect" "807f12b6fbafbd0b5ab69abfbc1f7204a79171585477f12733fa673c00cbad77"` Dec 06 04:56:04.857 INFO running `"docker" "rm" "-f" "807f12b6fbafbd0b5ab69abfbc1f7204a79171585477f12733fa673c00cbad77"` Dec 06 04:56:04.942 INFO [stdout] 807f12b6fbafbd0b5ab69abfbc1f7204a79171585477f12733fa673c00cbad77 Dec 06 04:56:04.944 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-7/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/pr-56514/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/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 +6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468-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:05.203 INFO [stdout] 697a8ef445f99600529344f4483e9d6b0593f450601e8019c952ea5f433a221c Dec 06 04:56:05.205 INFO running `"docker" "start" "-a" "697a8ef445f99600529344f4483e9d6b0593f450601e8019c952ea5f433a221c"` Dec 06 04:56:05.817 INFO [stderr] usermod: no changes Dec 06 04:56:05.848 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 06 04:56:05.848 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 06 04:56:05.848 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 06 04:56:05.848 INFO [stderr] files will be included as a binary target: Dec 06 04:56:05.848 INFO [stderr] Dec 06 04:56:05.848 INFO [stderr] * /source/src/main.rs Dec 06 04:56:05.848 INFO [stderr] Dec 06 04:56:05.848 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 06 04:56:05.848 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 06 04:56:05.848 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 06 04:56:05.848 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 06 04:56:05.848 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 06 04:56:05.848 INFO [stderr] Dec 06 04:56:05.848 INFO [stderr] For more information on this warning you can consult Dec 06 04:56:05.848 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 06 04:56:05.848 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `flatten-filenames`, Dec 06 04:56:05.848 INFO [stderr] please set bin.path in Cargo.toml Dec 06 04:56:05.849 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.02s Dec 06 04:56:05.850 INFO [stderr] Running /target/debug/deps/flatten_filenames-ea84629c3a213ddf Dec 06 04:56:05.852 INFO [stdout] Dec 06 04:56:05.852 INFO [stdout] running 10 tests Dec 06 04:56:05.853 INFO [stdout] test test::new_prefix_works ... ok Dec 06 04:56:05.853 INFO [stdout] test test::new_prefix_leading_dash_or_plus ... ok Dec 06 04:56:05.853 INFO [stdout] test test::new_prefix_empty_old_prefix ... ok Dec 06 04:56:05.853 INFO [stdout] test test::leading_char_for_filename ... ok Dec 06 04:56:05.856 INFO [stdout] test test::should_traverse_not_leading_dot_or_underscore ... ok Dec 06 04:56:05.860 INFO [stdout] test test::should_traverse_directory ... ok Dec 06 04:56:05.861 INFO [stdout] test test::rename_works ... ok Dec 06 04:56:05.863 INFO [stdout] test test::should_traverse_not_dir ... ok Dec 06 04:56:05.864 INFO [stdout] test test::rename_skips_dot_files ... ok Dec 06 04:56:05.867 INFO [stdout] test test::flatten_works ... ok Dec 06 04:56:05.867 INFO [stdout] Dec 06 04:56:05.867 INFO [stdout] test result: ok. 10 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 06 04:56:05.867 INFO [stdout] Dec 06 04:56:05.868 INFO [stderr] su: No module specific data is present Dec 06 04:56:06.189 INFO running `"docker" "inspect" "697a8ef445f99600529344f4483e9d6b0593f450601e8019c952ea5f433a221c"` Dec 06 04:56:06.290 INFO running `"docker" "rm" "-f" "697a8ef445f99600529344f4483e9d6b0593f450601e8019c952ea5f433a221c"` Dec 06 04:56:06.376 INFO [stdout] 697a8ef445f99600529344f4483e9d6b0593f450601e8019c952ea5f433a221c