[INFO] crate permutate 0.3.2 is already in cache [INFO] extracting crate permutate 0.3.2 into work/ex/beta-1.38-1/sources/1.37.0/reg/permutate/0.3.2 [INFO] extracting crate permutate 0.3.2 into work/ex/beta-1.38-1/sources/beta-2019-08-13/reg/permutate/0.3.2 [INFO] validating manifest of permutate-0.3.2 on toolchain 1.37.0 [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.37.0" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] validating manifest of permutate-0.3.2 on toolchain beta-2019-08-13 [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-08-13" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] started frobbing permutate-0.3.2 [INFO] finished frobbing permutate-0.3.2 [INFO] frobbed toml for permutate-0.3.2 written to work/ex/beta-1.38-1/sources/1.37.0/reg/permutate/0.3.2/Cargo.toml [INFO] started frobbing permutate-0.3.2 [INFO] finished frobbing permutate-0.3.2 [INFO] frobbed toml for permutate-0.3.2 written to work/ex/beta-1.38-1/sources/beta-2019-08-13/reg/permutate/0.3.2/Cargo.toml [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.37.0" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-08-13" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.37.0" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-08-13" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] testing permutate-0.3.2 against 1.37.0 for beta-1.38-1 [INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.38-1/worker-6/1.37.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.38-1/sources/1.37.0/reg/permutate/0.3.2:/opt/crater/workdir:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/opt/crater/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/opt/crater/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/opt/crater/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/crater/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/crater/cargo-home" "-e" "RUSTUP_HOME=/opt/crater/rustup-home" "-w" "/opt/crater/workdir" "-m" "1536M" "--network" "none" "rustops/crates-build-env" "/opt/crater/cargo-home/bin/cargo" "+1.37.0" "build" "--frozen"` [INFO] [stdout] 799f1d45f208ae0642c2526698bb197e4aa272bc41bba1f372d33b7779aba659 [INFO] running `"docker" "start" "-a" "799f1d45f208ae0642c2526698bb197e4aa272bc41bba1f372d33b7779aba659"` [INFO] [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other binary targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a binary target: [INFO] [stderr] [INFO] [stderr] * /opt/crater/workdir/src/bin/buffer.rs [INFO] [stderr] * /opt/crater/workdir/src/bin/man.rs [INFO] [stderr] * /opt/crater/workdir/src/bin/arguments.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 binary target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autobins = 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 permutate v0.3.2 (/opt/crater/workdir) [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 1.53s [INFO] running `"docker" "inspect" "799f1d45f208ae0642c2526698bb197e4aa272bc41bba1f372d33b7779aba659"` [INFO] running `"docker" "rm" "-f" "799f1d45f208ae0642c2526698bb197e4aa272bc41bba1f372d33b7779aba659"` [INFO] [stdout] 799f1d45f208ae0642c2526698bb197e4aa272bc41bba1f372d33b7779aba659 [INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.38-1/worker-6/1.37.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.38-1/sources/1.37.0/reg/permutate/0.3.2:/opt/crater/workdir:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/opt/crater/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/opt/crater/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/opt/crater/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/crater/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/crater/cargo-home" "-e" "RUSTUP_HOME=/opt/crater/rustup-home" "-w" "/opt/crater/workdir" "-m" "1536M" "--network" "none" "rustops/crates-build-env" "/opt/crater/cargo-home/bin/cargo" "+1.37.0" "test" "--frozen" "--no-run"` [INFO] [stdout] a54b7dca26a7fc908f783f23e9ff44a6284678e6fd9c07ed83c8f113cd1d8f32 [INFO] running `"docker" "start" "-a" "a54b7dca26a7fc908f783f23e9ff44a6284678e6fd9c07ed83c8f113cd1d8f32"` [INFO] [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other binary targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a binary target: [INFO] [stderr] [INFO] [stderr] * /opt/crater/workdir/src/bin/buffer.rs [INFO] [stderr] * /opt/crater/workdir/src/bin/man.rs [INFO] [stderr] * /opt/crater/workdir/src/bin/arguments.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 binary target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autobins = 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 permutate v0.3.2 (/opt/crater/workdir) [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 1.33s [INFO] running `"docker" "inspect" "a54b7dca26a7fc908f783f23e9ff44a6284678e6fd9c07ed83c8f113cd1d8f32"` [INFO] running `"docker" "rm" "-f" "a54b7dca26a7fc908f783f23e9ff44a6284678e6fd9c07ed83c8f113cd1d8f32"` [INFO] [stdout] a54b7dca26a7fc908f783f23e9ff44a6284678e6fd9c07ed83c8f113cd1d8f32 [INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.38-1/worker-6/1.37.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.38-1/sources/1.37.0/reg/permutate/0.3.2:/opt/crater/workdir:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/opt/crater/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/opt/crater/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/opt/crater/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/crater/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/crater/cargo-home" "-e" "RUSTUP_HOME=/opt/crater/rustup-home" "-w" "/opt/crater/workdir" "-m" "1536M" "--network" "none" "rustops/crates-build-env" "/opt/crater/cargo-home/bin/cargo" "+1.37.0" "test" "--frozen"` [INFO] [stdout] e1639ad09da8073c5fb4ebd305a6b3849af948ea18b606a5b7e5a722f3cf0902 [INFO] running `"docker" "start" "-a" "e1639ad09da8073c5fb4ebd305a6b3849af948ea18b606a5b7e5a722f3cf0902"` [INFO] [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other binary targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a binary target: [INFO] [stderr] [INFO] [stderr] * /opt/crater/workdir/src/bin/buffer.rs [INFO] [stderr] * /opt/crater/workdir/src/bin/man.rs [INFO] [stderr] * /opt/crater/workdir/src/bin/arguments.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 binary target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autobins = 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/crater/target/debug/deps/permutate-6f0a58a826afb073 [INFO] [stdout] [INFO] [stdout] running 4 tests [INFO] [stdout] test test::single_list_permutation ... ok [INFO] [stdout] test test::test_permutation_values ... ok [INFO] [stdout] test test::test_reset ... ok [INFO] [stdout] test test::test_million_permutations ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 4 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Running /opt/crater/target/debug/deps/permutate-cb8e02340309e815 [INFO] [stdout] running 1 test [INFO] [stderr] Doc-tests permutate [INFO] [stdout] test arguments::test::test_parse_arguments ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] running 3 tests [INFO] [stdout] test src/lib.rs - (line 22) ... ok [INFO] [stdout] test src/lib.rs - (line 87) ... ok [INFO] [stdout] test src/lib.rs - (line 51) ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 3 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out [INFO] [stdout] [INFO] running `"docker" "inspect" "e1639ad09da8073c5fb4ebd305a6b3849af948ea18b606a5b7e5a722f3cf0902"` [INFO] running `"docker" "rm" "-f" "e1639ad09da8073c5fb4ebd305a6b3849af948ea18b606a5b7e5a722f3cf0902"` [INFO] [stdout] e1639ad09da8073c5fb4ebd305a6b3849af948ea18b606a5b7e5a722f3cf0902