Nov 17 07:38:26.644 INFO testing brettcannon/flatten_filenames against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982 Nov 17 07:38:26.644 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-7/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-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.019 INFO [stdout] 590b3179c1c7637e0bdb332a93021e059b671d85c7a22513bb3af808f6df7082 Nov 17 07:38:27.029 INFO running `"docker" "start" "-a" "590b3179c1c7637e0bdb332a93021e059b671d85c7a22513bb3af808f6df7082"` Nov 17 07:38:27.583 INFO [stderr] usermod: no changes Nov 17 07:38:27.611 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 17 07:38:27.611 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 17 07:38:27.611 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 17 07:38:27.611 INFO [stderr] files will be included as a binary target: Nov 17 07:38:27.611 INFO [stderr] Nov 17 07:38:27.611 INFO [stderr] * /source/src/main.rs Nov 17 07:38:27.611 INFO [stderr] Nov 17 07:38:27.611 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 17 07:38:27.611 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 17 07:38:27.611 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 17 07:38:27.611 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 17 07:38:27.611 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 17 07:38:27.611 INFO [stderr] Nov 17 07:38:27.611 INFO [stderr] For more information on this warning you can consult Nov 17 07:38:27.611 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 17 07:38:27.611 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `flatten-filenames`, Nov 17 07:38:27.611 INFO [stderr] please set bin.path in Cargo.toml Nov 17 07:38:27.619 INFO [stderr] Compiling flatten_filenames v0.1.0 (/source) Nov 17 07:38:28.390 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.79s Nov 17 07:38:28.393 INFO [stderr] su: No module specific data is present Nov 17 07:38:28.769 INFO running `"docker" "inspect" "590b3179c1c7637e0bdb332a93021e059b671d85c7a22513bb3af808f6df7082"` Nov 17 07:38:28.831 INFO running `"docker" "rm" "-f" "590b3179c1c7637e0bdb332a93021e059b671d85c7a22513bb3af808f6df7082"` Nov 17 07:38:28.927 INFO [stdout] 590b3179c1c7637e0bdb332a93021e059b671d85c7a22513bb3af808f6df7082 Nov 17 07:38:28.929 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-7/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-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.113 INFO [stdout] 35c4997fff9ca7bb902f7ae9f307acb9feff1752c33f8eedac88c3b2e8828749 Nov 17 07:38:29.115 INFO running `"docker" "start" "-a" "35c4997fff9ca7bb902f7ae9f307acb9feff1752c33f8eedac88c3b2e8828749"` Nov 17 07:38:29.687 INFO [stderr] usermod: no changes Nov 17 07:38:29.707 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 17 07:38:29.707 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 17 07:38:29.707 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 17 07:38:29.707 INFO [stderr] files will be included as a binary target: Nov 17 07:38:29.707 INFO [stderr] Nov 17 07:38:29.707 INFO [stderr] * /source/src/main.rs Nov 17 07:38:29.707 INFO [stderr] Nov 17 07:38:29.707 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 17 07:38:29.707 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 17 07:38:29.707 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 17 07:38:29.707 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 17 07:38:29.707 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 17 07:38:29.707 INFO [stderr] Nov 17 07:38:29.707 INFO [stderr] For more information on this warning you can consult Nov 17 07:38:29.707 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 17 07:38:29.707 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `flatten-filenames`, Nov 17 07:38:29.707 INFO [stderr] please set bin.path in Cargo.toml Nov 17 07:38:29.715 INFO [stderr] Compiling rand v0.3.14 Nov 17 07:38:31.449 INFO [stderr] Compiling tempdir v0.3.5 Nov 17 07:38:31.847 INFO [stderr] Compiling flatten_filenames v0.1.0 (/source) Nov 17 07:38:32.876 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 3.18s Nov 17 07:38:32.879 INFO [stderr] su: No module specific data is present Nov 17 07:38:33.152 INFO running `"docker" "inspect" "35c4997fff9ca7bb902f7ae9f307acb9feff1752c33f8eedac88c3b2e8828749"` Nov 17 07:38:33.244 INFO running `"docker" "rm" "-f" "35c4997fff9ca7bb902f7ae9f307acb9feff1752c33f8eedac88c3b2e8828749"` Nov 17 07:38:33.349 INFO [stdout] 35c4997fff9ca7bb902f7ae9f307acb9feff1752c33f8eedac88c3b2e8828749 Nov 17 07:38:33.351 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-7/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-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:33.508 INFO [stdout] 0c3e232ebcf349bf78fb35e1ec253ac5e91a7ced165ce7efc495a2170b59277c Nov 17 07:38:33.509 INFO running `"docker" "start" "-a" "0c3e232ebcf349bf78fb35e1ec253ac5e91a7ced165ce7efc495a2170b59277c"` Nov 17 07:38:33.959 INFO [stderr] usermod: no changes Nov 17 07:38:33.978 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 17 07:38:33.978 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 17 07:38:33.978 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 17 07:38:33.978 INFO [stderr] files will be included as a binary target: Nov 17 07:38:33.978 INFO [stderr] Nov 17 07:38:33.979 INFO [stderr] * /source/src/main.rs Nov 17 07:38:33.979 INFO [stderr] Nov 17 07:38:33.979 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 17 07:38:33.979 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 17 07:38:33.979 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 17 07:38:33.979 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 17 07:38:33.979 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 17 07:38:33.979 INFO [stderr] Nov 17 07:38:33.979 INFO [stderr] For more information on this warning you can consult Nov 17 07:38:33.979 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 17 07:38:33.979 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `flatten-filenames`, Nov 17 07:38:33.979 INFO [stderr] please set bin.path in Cargo.toml Nov 17 07:38:33.983 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.01s Nov 17 07:38:33.983 INFO [stderr] Running /target/debug/deps/flatten_filenames-126a990560c1bbac Nov 17 07:38:33.988 INFO [stdout] Nov 17 07:38:33.988 INFO [stdout] running 10 tests Nov 17 07:38:33.988 INFO [stdout] test test::leading_char_for_filename ... ok Nov 17 07:38:33.989 INFO [stdout] test test::new_prefix_works ... ok Nov 17 07:38:33.991 INFO [stdout] test test::new_prefix_leading_dash_or_plus ... ok Nov 17 07:38:33.991 INFO [stdout] test test::new_prefix_empty_old_prefix ... ok Nov 17 07:38:33.991 INFO [stdout] test test::should_traverse_directory ... ok Nov 17 07:38:33.991 INFO [stdout] test test::should_traverse_not_leading_dot_or_underscore ... ok Nov 17 07:38:33.995 INFO [stdout] test test::rename_skips_dot_files ... ok Nov 17 07:38:33.995 INFO [stdout] test test::should_traverse_not_dir ... ok Nov 17 07:38:33.995 INFO [stdout] test test::rename_works ... ok Nov 17 07:38:33.999 INFO [stdout] test test::flatten_works ... ok Nov 17 07:38:33.999 INFO [stdout] Nov 17 07:38:33.999 INFO [stdout] test result: ok. 10 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Nov 17 07:38:33.999 INFO [stdout] Nov 17 07:38:34.002 INFO [stderr] su: No module specific data is present Nov 17 07:38:34.244 INFO running `"docker" "inspect" "0c3e232ebcf349bf78fb35e1ec253ac5e91a7ced165ce7efc495a2170b59277c"` Nov 17 07:38:34.336 INFO running `"docker" "rm" "-f" "0c3e232ebcf349bf78fb35e1ec253ac5e91a7ced165ce7efc495a2170b59277c"` Nov 17 07:38:34.410 INFO [stdout] 0c3e232ebcf349bf78fb35e1ec253ac5e91a7ced165ce7efc495a2170b59277c