[INFO] fetching crate html5ever 0.24.0... [INFO] extracting crate html5ever 0.24.0 into work/ex/beta-1.37-6/sources/1.36.0/reg/html5ever/0.24.0 [INFO] extracting crate html5ever 0.24.0 into work/ex/beta-1.37-6/sources/beta-2019-07-23/reg/html5ever/0.24.0 [INFO] validating manifest of html5ever-0.24.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 html5ever-0.24.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 html5ever-0.24.0 [INFO] removed 3 missing tests [INFO] finished frobbing html5ever-0.24.0 [INFO] frobbed toml for html5ever-0.24.0 written to work/ex/beta-1.37-6/sources/1.36.0/reg/html5ever/0.24.0/Cargo.toml [INFO] started frobbing html5ever-0.24.0 [INFO] removed 3 missing tests [INFO] finished frobbing html5ever-0.24.0 [INFO] frobbed toml for html5ever-0.24.0 written to work/ex/beta-1.37-6/sources/beta-2019-07-23/reg/html5ever/0.24.0/Cargo.toml [INFO] crate html5ever-0.24.0 already has a lockfile, it will not be regenerated [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.36.0" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] [stderr] Blocking waiting for file lock on package cache lock [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-07-23" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] testing html5ever-0.24.0 against beta-2019-07-23 for beta-1.37-6 [INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.37-6/worker-3/beta-2019-07-23:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.37-6/sources/beta-2019-07-23/reg/html5ever/0.24.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" "+beta-2019-07-23" "build" "--frozen"` [INFO] [stdout] ebfdac050d11922e5587fbb3c4e961948404cdef26de96bdd2b2f3847741c4d1 [INFO] running `"docker" "start" "-a" "ebfdac050d11922e5587fbb3c4e961948404cdef26de96bdd2b2f3847741c4d1"` [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/serializer.rs [INFO] [stderr] * /opt/crater/workdir/tests/tokenizer.rs [INFO] [stderr] * /opt/crater/workdir/tests/tree_builder.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 syn v0.15.40 [INFO] [stderr] Compiling log v0.4.7 [INFO] [stderr] Compiling serde_json v1.0.40 [INFO] [stderr] Compiling string_cache v0.7.3 [INFO] [stderr] Compiling serde_derive v1.0.97 [INFO] [stderr] Compiling html5ever v0.24.0 (/opt/crater/workdir) [INFO] [stderr] Compiling markup5ever v0.9.0 [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 50.11s [INFO] running `"docker" "inspect" "ebfdac050d11922e5587fbb3c4e961948404cdef26de96bdd2b2f3847741c4d1"` [INFO] running `"docker" "rm" "-f" "ebfdac050d11922e5587fbb3c4e961948404cdef26de96bdd2b2f3847741c4d1"` [INFO] [stdout] ebfdac050d11922e5587fbb3c4e961948404cdef26de96bdd2b2f3847741c4d1 [INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.37-6/worker-3/beta-2019-07-23:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.37-6/sources/beta-2019-07-23/reg/html5ever/0.24.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" "+beta-2019-07-23" "test" "--frozen" "--no-run"` [INFO] [stdout] 9f68b5001e7ac3a6b93b010d382de6a146d027a307e09962d1abc450e24a49a5 [INFO] running `"docker" "start" "-a" "9f68b5001e7ac3a6b93b010d382de6a146d027a307e09962d1abc450e24a49a5"` [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/serializer.rs [INFO] [stderr] * /opt/crater/workdir/tests/tokenizer.rs [INFO] [stderr] * /opt/crater/workdir/tests/tree_builder.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 typed-arena v1.4.1 [INFO] [stderr] Compiling crossbeam-epoch v0.7.1 [INFO] [stderr] Compiling regex-automata v0.1.7 [INFO] [stderr] Compiling rustc-test v0.3.0 [INFO] [stderr] Compiling tinytemplate v1.0.2 [INFO] [stderr] Compiling bstr v0.2.3 [INFO] [stderr] Compiling crossbeam-deque v0.6.3 [INFO] [stderr] Compiling rayon-core v1.5.0 [INFO] [stderr] Compiling rayon v1.1.0 [INFO] [stderr] Compiling csv v1.1.1 [INFO] [stderr] Compiling criterion v0.2.11 [INFO] [stderr] Compiling html5ever v0.24.0 (/opt/crater/workdir) [INFO] [stderr] warning: unused variable: `prev_element` [INFO] [stderr] --> examples/print-tree-actions.rs:109:9 [INFO] [stderr] | [INFO] [stderr] 109 | prev_element: &Self::Handle, [INFO] [stderr] | ^^^^^^^^^^^^ help: consider prefixing with an underscore: `_prev_element` [INFO] [stderr] | [INFO] [stderr] = note: #[warn(unused_variables)] on by default [INFO] [stderr] [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 35.40s [INFO] running `"docker" "inspect" "9f68b5001e7ac3a6b93b010d382de6a146d027a307e09962d1abc450e24a49a5"` [INFO] running `"docker" "rm" "-f" "9f68b5001e7ac3a6b93b010d382de6a146d027a307e09962d1abc450e24a49a5"` [INFO] [stdout] 9f68b5001e7ac3a6b93b010d382de6a146d027a307e09962d1abc450e24a49a5 [INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.37-6/worker-3/beta-2019-07-23:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.37-6/sources/beta-2019-07-23/reg/html5ever/0.24.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" "+beta-2019-07-23" "test" "--frozen"` [INFO] [stdout] b35a039e9737560e1410000d4f81f5cfa05cdce1c6b2247f39524d223c6515b5 [INFO] running `"docker" "start" "-a" "b35a039e9737560e1410000d4f81f5cfa05cdce1c6b2247f39524d223c6515b5"` [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/serializer.rs [INFO] [stderr] * /opt/crater/workdir/tests/tokenizer.rs [INFO] [stderr] * /opt/crater/workdir/tests/tree_builder.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.07s [INFO] [stderr] Running /opt/crater/target/debug/deps/html5ever-e9132b9627a82dce [INFO] [stdout] [INFO] [stdout] running 16 tests [INFO] [stdout] test tokenizer::test::push_to_None_gives_singleton ... ok [INFO] [stdout] test tokenizer::test::check_lines ... ok [INFO] [stdout] test util::str::test::is_alnum_1 ... ok [INFO] [stdout] test util::str::test::is_alnum_A ... ok [INFO] [stdout] test tokenizer::test::push_to_empty_appends ... ok [INFO] [stdout] test util::str::test::is_alnum_a ... ok [INFO] [stdout] test tokenizer::test::push_to_nonempty_appends ... ok [INFO] [stdout] test tree_builder::test::check_four_lines ... ok [INFO] [stdout] test util::str::test::lower_letter_a_is_a ... ok [INFO] [stdout] test util::str::test::lower_letter_A_is_a ... ok [INFO] [stdout] test tokenizer::test::check_lines_with_new_line ... ok [INFO] [stdout] test driver::tests::from_utf8 ... ok [INFO] [stdout] test util::str::test::lower_letter_nonascii_is_None ... ok [INFO] [stdout] test util::str::test::is_not_alnum_symbol ... ok [INFO] [stdout] test util::str::test::lower_letter_symbol_is_None ... ok [INFO] [stdout] test util::str::test::is_not_alnum_nonascii ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 16 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out [INFO] [stdout] [INFO] [stderr] Doc-tests html5ever [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" "b35a039e9737560e1410000d4f81f5cfa05cdce1c6b2247f39524d223c6515b5"` [INFO] running `"docker" "rm" "-f" "b35a039e9737560e1410000d4f81f5cfa05cdce1c6b2247f39524d223c6515b5"` [INFO] [stdout] b35a039e9737560e1410000d4f81f5cfa05cdce1c6b2247f39524d223c6515b5