[INFO] crate valico 3.0.0 is already in cache [INFO] extracting crate valico 3.0.0 into work/ex/beta-1.37-6/sources/1.36.0/reg/valico/3.0.0 [INFO] extracting crate valico 3.0.0 into work/ex/beta-1.37-6/sources/beta-2019-07-23/reg/valico/3.0.0 [INFO] validating manifest of valico-3.0.0 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 valico-3.0.0 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 valico-3.0.0 [INFO] removed 1 missing tests [INFO] finished frobbing valico-3.0.0 [INFO] frobbed toml for valico-3.0.0 written to work/ex/beta-1.37-6/sources/1.36.0/reg/valico/3.0.0/Cargo.toml [INFO] started frobbing valico-3.0.0 [INFO] removed 1 missing tests [INFO] finished frobbing valico-3.0.0 [INFO] frobbed toml for valico-3.0.0 written to work/ex/beta-1.37-6/sources/beta-2019-07-23/reg/valico/3.0.0/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] 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 valico-3.0.0 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-7/1.36.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.37-6/sources/1.36.0/reg/valico/3.0.0:/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] bbb326335e515572a732278bc1a4504511e66e5e511a6ca277b2c0a0977d843a [INFO] running `"docker" "start" "-a" "bbb326335e515572a732278bc1a4504511e66e5e511a6ca277b2c0a0977d843a"` [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/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 jsonway v2.0.0 [INFO] [stderr] Compiling valico v3.0.0 (/opt/crater/workdir) [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 6.73s [INFO] running `"docker" "inspect" "bbb326335e515572a732278bc1a4504511e66e5e511a6ca277b2c0a0977d843a"` [INFO] running `"docker" "rm" "-f" "bbb326335e515572a732278bc1a4504511e66e5e511a6ca277b2c0a0977d843a"` [INFO] [stdout] bbb326335e515572a732278bc1a4504511e66e5e511a6ca277b2c0a0977d843a [INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.37-6/worker-7/1.36.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.37-6/sources/1.36.0/reg/valico/3.0.0:/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] 08054dbcd1074d32e9ea696062be83ff3bb627013bf38c5b89f067bc38c73f6b [INFO] running `"docker" "start" "-a" "08054dbcd1074d32e9ea696062be83ff3bb627013bf38c5b89f067bc38c73f6b"` [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/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 valico v3.0.0 (/opt/crater/workdir) [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 7.01s [INFO] running `"docker" "inspect" "08054dbcd1074d32e9ea696062be83ff3bb627013bf38c5b89f067bc38c73f6b"` [INFO] running `"docker" "rm" "-f" "08054dbcd1074d32e9ea696062be83ff3bb627013bf38c5b89f067bc38c73f6b"` [INFO] [stdout] 08054dbcd1074d32e9ea696062be83ff3bb627013bf38c5b89f067bc38c73f6b [INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.37-6/worker-7/1.36.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.37-6/sources/1.36.0/reg/valico/3.0.0:/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] 761006a736344669fcf77e3740b5d72be00db1e800c51c1f127ab54f401f0980 [INFO] running `"docker" "start" "-a" "761006a736344669fcf77e3740b5d72be00db1e800c51c1f127ab54f401f0980"` [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/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.05s [INFO] [stderr] Running /opt/crater/target/debug/deps/valico-8c04e3614f77084c [INFO] [stdout] [INFO] [stdout] running 64 tests [INFO] [stdout] test json_schema::keywords::enum_::malformed ... ok [INFO] [stdout] test json_schema::keywords::dependencies::validate_dependencies ... ok [INFO] [stdout] test json_schema::keywords::dependencies::malformed ... ok [INFO] [stdout] test json_schema::keywords::format::validate_ipv6 ... ok [INFO] [stdout] test json_schema::keywords::format::validate_date_time ... ok [INFO] [stdout] test json_schema::keywords::items::validate_items_with_array_of_schemes ... ok [INFO] [stdout] test json_schema::keywords::enum_::validate ... ok [INFO] [stdout] test json_schema::keywords::items::validate_items_with_array_of_schemes_with_additional_bool ... ok [INFO] [stdout] test json_schema::keywords::maxmin::mailformed_exclusive_maximum ... ok [INFO] [stdout] test json_schema::keywords::items::validate_items_with_schema ... ok [INFO] [stdout] test json_schema::keywords::format::validate_uri ... ok [INFO] [stdout] test json_schema::keywords::format::validate_hostname ... ok [INFO] [stdout] test json_schema::keywords::format::validate_email ... ok [INFO] [stdout] test json_schema::keywords::format::validate_uuid ... ok [INFO] [stdout] test json_schema::keywords::format::validate_ipv4 ... ok [INFO] [stdout] test json_schema::keywords::items::validate_items_with_array_of_schemes_with_additional_schema ... ok [INFO] [stdout] test json_schema::keywords::maxmin::mailformed_maximum ... ok [INFO] [stdout] test json_schema::keywords::maxmin::validate_maximum ... ok [INFO] [stdout] test json_schema::keywords::maxmin_items::validate_max_items ... ok [INFO] [stdout] test json_schema::keywords::maxmin::mailformed_exclusive_minumum ... ok [INFO] [stdout] test json_schema::keywords::maxmin_items::malformed_min_items ... ok [INFO] [stdout] test json_schema::keywords::maxmin::validate_exclusive_maximum ... ok [INFO] [stdout] test json_schema::keywords::maxmin::mailformed_minumum ... ok [INFO] [stdout] test json_schema::keywords::maxmin::validate_exclusive_minimum ... ok [INFO] [stdout] test json_schema::keywords::maxmin_items::malformed_max_items ... ok [INFO] [stdout] test json_schema::keywords::maxmin_properties::malformed_min_properties ... ok [INFO] [stdout] test json_schema::keywords::maxmin_length::validate_min_length ... ok [INFO] [stdout] test json_schema::keywords::maxmin_properties::validate_max_properties ... ok [INFO] [stdout] test json_schema::keywords::maxmin::validate_minumum ... ok [INFO] [stdout] test json_schema::keywords::maxmin_length::malformed_min_length ... ok [INFO] [stdout] test json_schema::keywords::maxmin_length::validate_max_length ... ok [INFO] [stdout] test json_schema::keywords::maxmin_items::validate_min_items ... ok [INFO] [stdout] test json_schema::keywords::multiple_of::malformed ... ok [INFO] [stdout] test json_schema::keywords::maxmin_length::malformed_max_length ... ok [INFO] [stdout] test json_schema::keywords::of::validate_any_of ... ok [INFO] [stdout] test json_schema::keywords::multiple_of::validate ... ok [INFO] [stdout] test json_schema::keywords::of::validate_one_of ... ok [INFO] [stdout] test json_schema::keywords::of::validate_all_of ... ok [INFO] [stdout] test json_schema::keywords::maxmin_properties::malformed_max_properties ... ok [INFO] [stdout] test json_schema::keywords::maxmin_properties::validate_min_properties ... ok [INFO] [stdout] test json_schema::keywords::properties::validate_pattern_properties ... ok [INFO] [stdout] test json_schema::keywords::properties::malformed ... ok [INFO] [stdout] test json_schema::keywords::pattern::mailformed ... ok [INFO] [stdout] test json_schema::keywords::pattern::validate ... ok [INFO] [stdout] test json_schema::keywords::required::malformed ... ok [INFO] [stdout] test json_schema::keywords::properties::validate_properties ... ok [INFO] [stdout] test json_schema::keywords::required::validate ... ok [INFO] [stdout] test json_schema::keywords::type_::validate_boolean ... ok [INFO] [stdout] test json_schema::keywords::ref_::validate ... ok [INFO] [stdout] test json_schema::keywords::type_::validate_array ... ok [INFO] [stdout] test json_schema::keywords::type_::validate_integer ... ok [INFO] [stdout] test json_schema::keywords::type_::validate_number ... ok [INFO] [stdout] test json_schema::keywords::type_::validate_null ... ok [INFO] [stdout] test json_schema::keywords::properties::validate_kw_properties ... ok [INFO] [stdout] test json_schema::keywords::type_::malformed ... ok [INFO] [stdout] test json_schema::keywords::properties::validate_additional_properties_schema ... ok [INFO] [stdout] test json_schema::keywords::properties::validate_additional_properties_false ... ok [INFO] [stdout] test json_schema::schema::schema_doesnt_compile_not_object ... ok [INFO] [stdout] test json_schema::keywords::type_::validate_set ... ok [INFO] [stdout] test json_schema::keywords::type_::validate_object ... ok [INFO] [stdout] test json_schema::schema::schema_compiles_boolean_schema ... ok [INFO] [stdout] test json_schema::keywords::unique_items::validate_unique_items ... ok [INFO] [stdout] test json_schema::keywords::type_::validate_string ... ok [INFO] [stdout] test json_schema::scope::lookup ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 64 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out [INFO] [stdout] [INFO] [stderr] Doc-tests valico [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" "761006a736344669fcf77e3740b5d72be00db1e800c51c1f127ab54f401f0980"` [INFO] running `"docker" "rm" "-f" "761006a736344669fcf77e3740b5d72be00db1e800c51c1f127ab54f401f0980"` [INFO] [stdout] 761006a736344669fcf77e3740b5d72be00db1e800c51c1f127ab54f401f0980