[INFO] fetching crate log 0.4.7...
[INFO] extracting crate log 0.4.7 into work/ex/beta-1.37-6/sources/1.36.0/reg/log/0.4.7
[INFO] extracting crate log 0.4.7 into work/ex/beta-1.37-6/sources/beta-2019-07-23/reg/log/0.4.7
[INFO] validating manifest of log-0.4.7 on toolchain 1.36.0
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.36.0" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] validating manifest of log-0.4.7 on toolchain beta-2019-07-23
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-07-23" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] started frobbing log-0.4.7
[INFO] removed 1 missing tests
[INFO] finished frobbing log-0.4.7
[INFO] frobbed toml for log-0.4.7 written to work/ex/beta-1.37-6/sources/1.36.0/reg/log/0.4.7/Cargo.toml
[INFO] started frobbing log-0.4.7
[INFO] removed 1 missing tests
[INFO] finished frobbing log-0.4.7
[INFO] frobbed toml for log-0.4.7 written to work/ex/beta-1.37-6/sources/beta-2019-07-23/reg/log/0.4.7/Cargo.toml
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.36.0" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"`
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-07-23" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.36.0" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-07-23" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] testing log-0.4.7 against 1.36.0 for beta-1.37-6
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.37-6/worker-0/1.36.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.37-6/sources/1.36.0/reg/log/0.4.7:/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.36.0" "build" "--frozen"`
[INFO] [stdout] 48711a04897073e76022ad2c189ad6e503146e906c85047a9838d63532c8f50d
[INFO] running `"docker" "start" "-a" "48711a04897073e76022ad2c189ad6e503146e906c85047a9838d63532c8f50d"`
[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/crater/workdir/tests/filters.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]     Blocking waiting for file lock on package cache lock
[INFO] [stderr]     Blocking waiting for file lock on package cache lock
[INFO] [stderr]    Compiling log v0.4.7 (/opt/crater/workdir)
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.84s
[INFO] running `"docker" "inspect" "48711a04897073e76022ad2c189ad6e503146e906c85047a9838d63532c8f50d"`
[INFO] running `"docker" "rm" "-f" "48711a04897073e76022ad2c189ad6e503146e906c85047a9838d63532c8f50d"`
[INFO] [stdout] 48711a04897073e76022ad2c189ad6e503146e906c85047a9838d63532c8f50d
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.37-6/worker-0/1.36.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.37-6/sources/1.36.0/reg/log/0.4.7:/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.36.0" "test" "--frozen" "--no-run"`
[INFO] [stdout] 1de2b205f254db2539b855bebec6194ce154ed6bd6a40708c0656377cddf188a
[INFO] running `"docker" "start" "-a" "1de2b205f254db2539b855bebec6194ce154ed6bd6a40708c0656377cddf188a"`
[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/crater/workdir/tests/filters.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 log v0.4.7 (/opt/crater/workdir)
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.18s
[INFO] running `"docker" "inspect" "1de2b205f254db2539b855bebec6194ce154ed6bd6a40708c0656377cddf188a"`
[INFO] running `"docker" "rm" "-f" "1de2b205f254db2539b855bebec6194ce154ed6bd6a40708c0656377cddf188a"`
[INFO] [stdout] 1de2b205f254db2539b855bebec6194ce154ed6bd6a40708c0656377cddf188a
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.37-6/worker-0/1.36.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.37-6/sources/1.36.0/reg/log/0.4.7:/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.36.0" "test" "--frozen"`
[INFO] [stdout] 1a897fba5116f6a0749e9102da501dd09d742ea6044ae503c5f9f7798973b745
[INFO] running `"docker" "start" "-a" "1a897fba5116f6a0749e9102da501dd09d742ea6044ae503c5f9f7798973b745"`
[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/crater/workdir/tests/filters.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/crater/target/debug/deps/log-c40f4015858fd36b
[INFO] [stdout] 
[INFO] [stdout] running 13 tests
[INFO] [stdout] test tests::test_cross_eq ... ok
[INFO] [stdout] test tests::test_level_show ... ok
[INFO] [stdout] test tests::test_level_from_str ... ok
[INFO] [stdout] test tests::test_cross_cmp ... ok
[INFO] [stdout] test tests::test_levelfilter_from_str ... ok
[INFO] [stdout] test tests::test_metadata_convenience_builder ... ok
[INFO] [stdout] test tests::test_record_complete_builder ... ok
[INFO] [stdout] test tests::test_record_convenience_builder ... ok
[INFO] [stdout] test tests::test_record_builder ... ok
[INFO] [stdout] test tests::test_levelfilter_show ... ok
[INFO] [stdout] test tests::test_metadata_builder ... ok
[INFO] [stdout] test tests::test_to_level_filter ... ok
[INFO] [stdout] test tests::test_to_level ... ok
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 13 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
[INFO] [stdout] 
[INFO] [stderr]    Doc-tests log
[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" "1a897fba5116f6a0749e9102da501dd09d742ea6044ae503c5f9f7798973b745"`
[INFO] running `"docker" "rm" "-f" "1a897fba5116f6a0749e9102da501dd09d742ea6044ae503c5f9f7798973b745"`
[INFO] [stdout] 1a897fba5116f6a0749e9102da501dd09d742ea6044ae503c5f9f7798973b745