[INFO] updating cached repository https://github.com/mcasper/git-clean [INFO] running `"git" "-c" "credential.helper=" "-c" "credential.helper=/big/crater/work/cargo-home/bin/git-credential-null" "-c" "remote.origin.fetch=refs/heads/*:refs/heads/*" "fetch" "origin" "--force" "--prune"` [INFO] running `"git" "rev-parse" "HEAD"` [INFO] [stdout] 529ae3964738fa47d92cc9259f6291d5b9e41363 [INFO] testing mcasper/git-clean against beta-2019-09-28 for beta-1.39-1 [INFO] running `"git" "clone" "work/cache/git-repos/https%3A%2F%2Fgithub.com%2Fmcasper%2Fgit-clean" "work/builds/worker-1/source"` [INFO] [stderr] Cloning into 'work/builds/worker-1/source'... [INFO] [stderr] done. [INFO] validating manifest of git repo https://github.com/mcasper/git-clean on toolchain beta-2019-09-28 [INFO] running `"/big/crater/work/cargo-home/bin/cargo" "+beta-2019-09-28" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] started tweaking git repo https://github.com/mcasper/git-clean [INFO] removed 1 missing tests [INFO] finished tweaking git repo https://github.com/mcasper/git-clean [INFO] tweaked toml for git repo https://github.com/mcasper/git-clean written to work/builds/worker-1/source/Cargo.toml [INFO] crate git repo https://github.com/mcasper/git-clean already has a lockfile, it will not be regenerated [INFO] running `"/big/crater/work/cargo-home/bin/cargo" "+beta-2019-09-28" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other test targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a test target: [INFO] [stderr] [INFO] [stderr] * /big/crater/work/builds/worker-1/source/tests/support.rs [INFO] [stderr] * /big/crater/work/builds/worker-1/source/tests/remote.rs [INFO] [stderr] * /big/crater/work/builds/worker-1/source/tests/utility.rs [INFO] [stderr] * /big/crater/work/builds/worker-1/source/tests/deletion.rs [INFO] [stderr] * /big/crater/work/builds/worker-1/source/tests/local.rs [INFO] [stderr] * /big/crater/work/builds/worker-1/source/tests/tests.rs [INFO] [stderr] [INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be [INFO] [stderr] ready to be compiled as a test target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autotests = false` to your [package] [INFO] [stderr] section. You may also move the files to a location where Cargo would not [INFO] [stderr] automatically infer them to be a target, such as in subfolders. [INFO] [stderr] [INFO] [stderr] For more information on this warning you can consult [INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330 [INFO] running `"docker" "create" "-v" "/big/crater/work/builds/worker-1/target:/opt/rustwide/target:rw,Z" "-v" "/big/crater/work/builds/worker-1/source:/opt/rustwide/workdir:ro,Z" "-v" "/big/crater/work/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/big/crater/work/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--network" "none" "rustops/crates-build-env" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2019-09-28" "build" "--frozen"` [INFO] [stdout] 2c11cb9b24650383842529074ca86d8873de2b85a0663188d5c303d450c356e8 [INFO] running `"docker" "start" "-a" "2c11cb9b24650383842529074ca86d8873de2b85a0663188d5c303d450c356e8"` [INFO] [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other test targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a test target: [INFO] [stderr] [INFO] [stderr] * /opt/rustwide/workdir/tests/support.rs [INFO] [stderr] * /opt/rustwide/workdir/tests/remote.rs [INFO] [stderr] * /opt/rustwide/workdir/tests/utility.rs [INFO] [stderr] * /opt/rustwide/workdir/tests/deletion.rs [INFO] [stderr] * /opt/rustwide/workdir/tests/local.rs [INFO] [stderr] * /opt/rustwide/workdir/tests/tests.rs [INFO] [stderr] [INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be [INFO] [stderr] ready to be compiled as a test target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autotests = false` to your [package] [INFO] [stderr] section. You may also move the files to a location where Cargo would not [INFO] [stderr] automatically infer them to be a target, such as in subfolders. [INFO] [stderr] [INFO] [stderr] For more information on this warning you can consult [INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330 [INFO] [stderr] Compiling vec_map v0.7.0 [INFO] [stderr] Compiling atty v0.2.2 [INFO] [stderr] Compiling term_size v0.3.0 [INFO] [stderr] Compiling clap v2.23.3 [INFO] [stderr] Compiling git-clean v0.5.2 (/opt/rustwide/workdir) [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 10.26s [INFO] running `"docker" "inspect" "2c11cb9b24650383842529074ca86d8873de2b85a0663188d5c303d450c356e8"` [INFO] running `"docker" "rm" "-f" "2c11cb9b24650383842529074ca86d8873de2b85a0663188d5c303d450c356e8"` [INFO] [stdout] 2c11cb9b24650383842529074ca86d8873de2b85a0663188d5c303d450c356e8 [INFO] running `"docker" "create" "-v" "/big/crater/work/builds/worker-1/target:/opt/rustwide/target:rw,Z" "-v" "/big/crater/work/builds/worker-1/source:/opt/rustwide/workdir:ro,Z" "-v" "/big/crater/work/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/big/crater/work/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--network" "none" "rustops/crates-build-env" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2019-09-28" "test" "--frozen" "--no-run"` [INFO] [stdout] cddeb4b7eb6831a034d1445056a780ae3b88aeaf609171c9e4d6186d85647f6b [INFO] running `"docker" "start" "-a" "cddeb4b7eb6831a034d1445056a780ae3b88aeaf609171c9e4d6186d85647f6b"` [INFO] [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other test targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a test target: [INFO] [stderr] [INFO] [stderr] * /opt/rustwide/workdir/tests/support.rs [INFO] [stderr] * /opt/rustwide/workdir/tests/remote.rs [INFO] [stderr] * /opt/rustwide/workdir/tests/utility.rs [INFO] [stderr] * /opt/rustwide/workdir/tests/deletion.rs [INFO] [stderr] * /opt/rustwide/workdir/tests/local.rs [INFO] [stderr] * /opt/rustwide/workdir/tests/tests.rs [INFO] [stderr] [INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be [INFO] [stderr] ready to be compiled as a test target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autotests = false` to your [package] [INFO] [stderr] section. You may also move the files to a location where Cargo would not [INFO] [stderr] automatically infer them to be a target, such as in subfolders. [INFO] [stderr] [INFO] [stderr] For more information on this warning you can consult [INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330 [INFO] [stderr] Compiling tempdir v0.3.5 [INFO] [stderr] Compiling git-clean v0.5.2 (/opt/rustwide/workdir) [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 1.75s [INFO] running `"docker" "inspect" "cddeb4b7eb6831a034d1445056a780ae3b88aeaf609171c9e4d6186d85647f6b"` [INFO] running `"docker" "rm" "-f" "cddeb4b7eb6831a034d1445056a780ae3b88aeaf609171c9e4d6186d85647f6b"` [INFO] [stdout] cddeb4b7eb6831a034d1445056a780ae3b88aeaf609171c9e4d6186d85647f6b [INFO] running `"docker" "create" "-v" "/big/crater/work/builds/worker-1/target:/opt/rustwide/target:rw,Z" "-v" "/big/crater/work/builds/worker-1/source:/opt/rustwide/workdir:ro,Z" "-v" "/big/crater/work/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/big/crater/work/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--network" "none" "rustops/crates-build-env" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2019-09-28" "test" "--frozen"` [INFO] [stdout] e8480af0cc15575ecef68cf388780fe2aa4a14cadbec636cbab9a85a8b42cf1a [INFO] running `"docker" "start" "-a" "e8480af0cc15575ecef68cf388780fe2aa4a14cadbec636cbab9a85a8b42cf1a"` [INFO] [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other test targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a test target: [INFO] [stderr] [INFO] [stderr] * /opt/rustwide/workdir/tests/support.rs [INFO] [stderr] * /opt/rustwide/workdir/tests/remote.rs [INFO] [stderr] * /opt/rustwide/workdir/tests/utility.rs [INFO] [stderr] * /opt/rustwide/workdir/tests/deletion.rs [INFO] [stderr] * /opt/rustwide/workdir/tests/local.rs [INFO] [stderr] * /opt/rustwide/workdir/tests/tests.rs [INFO] [stderr] [INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be [INFO] [stderr] ready to be compiled as a test target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autotests = false` to your [package] [INFO] [stderr] section. You may also move the files to a location where Cargo would not [INFO] [stderr] automatically infer them to be a target, such as in subfolders. [INFO] [stderr] [INFO] [stderr] For more information on this warning you can consult [INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330 [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.01s [INFO] [stderr] Running /opt/rustwide/target/debug/deps/git_clean-4a6ad93e49f2aa44 [INFO] [stdout] [INFO] [stdout] running 12 tests [INFO] [stdout] test branches::test::test_branches_new ... ok [INFO] [stdout] test branches::test::test_format_single_column ... ok [INFO] [stdout] test branches::test::test_branches_of_bigger_lengths ... ok [INFO] [stdout] test branches::test::test_format_maxes_at_three_columns ... ok [INFO] [stdout] test branches::test::test_format_three_columns ... ok [INFO] [stdout] test branches::test::test_format_two_columns ... ok [INFO] [stdout] test branches::test::test_long_branches_with_three_columns ... ok [INFO] [stdout] test options::test::test_delete_mode_warning_message ... ok [INFO] [stdout] test branches::test::test_branches_of_different_lengths ... ok [INFO] [stdout] test options::test::test_delete_mode_new ... ok [INFO] [stdout] test commands::test::test_spawn_piped ... ok [INFO] [stdout] test options::test::test_git_options_new ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 12 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out [INFO] [stdout] [INFO] [stderr] Running /opt/rustwide/target/debug/deps/git_clean-edd2cb428f4b4cef [INFO] [stdout] [INFO] [stdout] running 0 tests [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out [INFO] [stdout] [INFO] [stderr] Doc-tests git-clean [INFO] [stdout] [INFO] [stdout] running 0 tests [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out [INFO] [stdout] [INFO] running `"docker" "inspect" "e8480af0cc15575ecef68cf388780fe2aa4a14cadbec636cbab9a85a8b42cf1a"` [INFO] running `"docker" "rm" "-f" "e8480af0cc15575ecef68cf388780fe2aa4a14cadbec636cbab9a85a8b42cf1a"` [INFO] [stdout] e8480af0cc15575ecef68cf388780fe2aa4a14cadbec636cbab9a85a8b42cf1a