Nov 17 05:49:37.413 INFO testing cstorey/spki-sexp.rs against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982
Nov 17 05:49:37.413 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-3/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +2e026d6e5d7621634147ad4c8074f1d964dbb1be-alt build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Nov 17 05:49:37.638 INFO [stdout] ea7ced43fb0bfdcf14faccc5edd8bc99e6d7353da8cf858597a4b639339483e4
Nov 17 05:49:37.640 INFO running `"docker" "start" "-a" "ea7ced43fb0bfdcf14faccc5edd8bc99e6d7353da8cf858597a4b639339483e4"`
Nov 17 05:49:38.019 INFO [stderr] usermod: no changes
Nov 17 05:49:38.058 INFO [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently
Nov 17 05:49:38.058 INFO [stderr] disables Cargo from automatically inferring other test targets.
Nov 17 05:49:38.058 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 17 05:49:38.058 INFO [stderr] files will be included as a test target:
Nov 17 05:49:38.058 INFO [stderr] 
Nov 17 05:49:38.058 INFO [stderr] * /source/tests/lib_types.rs
Nov 17 05:49:38.058 INFO [stderr] * /source/tests/lib_types.in.rs
Nov 17 05:49:38.058 INFO [stderr] 
Nov 17 05:49:38.058 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 17 05:49:38.058 INFO [stderr] ready to be compiled as a test target today. You can future-proof yourself
Nov 17 05:49:38.058 INFO [stderr] and disable this warning by adding `autotests = false` to your [package]
Nov 17 05:49:38.058 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 17 05:49:38.058 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 17 05:49:38.058 INFO [stderr] 
Nov 17 05:49:38.058 INFO [stderr] For more information on this warning you can consult
Nov 17 05:49:38.058 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 17 05:49:38.165 INFO [stderr]    Compiling syntex_pos v0.50.0
Nov 17 05:49:38.166 INFO [stderr]    Compiling error-chain v0.5.0
Nov 17 05:49:39.050 INFO [stderr]    Compiling syntex_errors v0.50.0
Nov 17 05:49:41.255 INFO [stderr]    Compiling syntex_syntax v0.50.0
Nov 17 05:50:27.232 INFO [stderr]    Compiling syntex v0.50.0
Nov 17 05:50:29.107 INFO [stderr]    Compiling serde_codegen v0.8.19
Nov 17 05:50:35.343 INFO [stderr]    Compiling spki-sexp v0.0.1 (/source)
Nov 17 05:50:42.576 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1m 04s
Nov 17 05:50:42.599 INFO [stderr] su: No module specific data is present
Nov 17 05:50:43.243 INFO running `"docker" "inspect" "ea7ced43fb0bfdcf14faccc5edd8bc99e6d7353da8cf858597a4b639339483e4"`
Nov 17 05:50:43.429 INFO running `"docker" "rm" "-f" "ea7ced43fb0bfdcf14faccc5edd8bc99e6d7353da8cf858597a4b639339483e4"`
Nov 17 05:50:43.736 INFO [stdout] ea7ced43fb0bfdcf14faccc5edd8bc99e6d7353da8cf858597a4b639339483e4
Nov 17 05:50:43.741 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-3/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +2e026d6e5d7621634147ad4c8074f1d964dbb1be-alt test --frozen --no-run" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Nov 17 05:50:44.207 INFO [stdout] 215f5b057f801762f477ba48c060fae09f9a39d1c0c80ef4aa4a4d48bb2874da
Nov 17 05:50:44.210 INFO running `"docker" "start" "-a" "215f5b057f801762f477ba48c060fae09f9a39d1c0c80ef4aa4a4d48bb2874da"`
Nov 17 05:50:45.035 INFO [stderr] usermod: no changes
Nov 17 05:50:45.067 INFO [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently
Nov 17 05:50:45.067 INFO [stderr] disables Cargo from automatically inferring other test targets.
Nov 17 05:50:45.068 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 17 05:50:45.068 INFO [stderr] files will be included as a test target:
Nov 17 05:50:45.068 INFO [stderr] 
Nov 17 05:50:45.068 INFO [stderr] * /source/tests/lib_types.rs
Nov 17 05:50:45.069 INFO [stderr] * /source/tests/lib_types.in.rs
Nov 17 05:50:45.069 INFO [stderr] 
Nov 17 05:50:45.069 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 17 05:50:45.069 INFO [stderr] ready to be compiled as a test target today. You can future-proof yourself
Nov 17 05:50:45.070 INFO [stderr] and disable this warning by adding `autotests = false` to your [package]
Nov 17 05:50:45.070 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 17 05:50:45.070 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 17 05:50:45.070 INFO [stderr] 
Nov 17 05:50:45.071 INFO [stderr] For more information on this warning you can consult
Nov 17 05:50:45.071 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 17 05:50:45.135 INFO [stderr]    Compiling quickcheck v0.3.2
Nov 17 05:50:47.805 INFO [stderr]    Compiling spki-sexp v0.0.1 (/source)
Nov 17 05:50:57.923 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 12.86s
Nov 17 05:50:57.927 INFO [stderr] su: No module specific data is present
Nov 17 05:50:58.847 INFO running `"docker" "inspect" "215f5b057f801762f477ba48c060fae09f9a39d1c0c80ef4aa4a4d48bb2874da"`
Nov 17 05:50:59.139 INFO running `"docker" "rm" "-f" "215f5b057f801762f477ba48c060fae09f9a39d1c0c80ef4aa4a4d48bb2874da"`
Nov 17 05:50:59.518 INFO [stdout] 215f5b057f801762f477ba48c060fae09f9a39d1c0c80ef4aa4a4d48bb2874da
Nov 17 05:50:59.525 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-3/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +2e026d6e5d7621634147ad4c8074f1d964dbb1be-alt test --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Nov 17 05:51:00.131 INFO [stdout] ead584bed598d57c8cdb875dd1add4fbab57c777f629ce5361deb8a46e62ee22
Nov 17 05:51:00.131 INFO running `"docker" "start" "-a" "ead584bed598d57c8cdb875dd1add4fbab57c777f629ce5361deb8a46e62ee22"`
Nov 17 05:51:01.252 INFO [stderr] usermod: no changes
Nov 17 05:51:01.330 INFO [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently
Nov 17 05:51:01.330 INFO [stderr] disables Cargo from automatically inferring other test targets.
Nov 17 05:51:01.330 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 17 05:51:01.330 INFO [stderr] files will be included as a test target:
Nov 17 05:51:01.330 INFO [stderr] 
Nov 17 05:51:01.330 INFO [stderr] * /source/tests/lib_types.rs
Nov 17 05:51:01.330 INFO [stderr] * /source/tests/lib_types.in.rs
Nov 17 05:51:01.330 INFO [stderr] 
Nov 17 05:51:01.330 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 17 05:51:01.330 INFO [stderr] ready to be compiled as a test target today. You can future-proof yourself
Nov 17 05:51:01.330 INFO [stderr] and disable this warning by adding `autotests = false` to your [package]
Nov 17 05:51:01.330 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 17 05:51:01.330 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 17 05:51:01.330 INFO [stderr] 
Nov 17 05:51:01.330 INFO [stderr] For more information on this warning you can consult
Nov 17 05:51:01.330 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 17 05:51:01.447 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.15s
Nov 17 05:51:01.463 INFO [stderr]      Running /target/debug/deps/spki_sexp-7b7616d29dfbeb29
Nov 17 05:51:01.472 INFO [stdout] 
Nov 17 05:51:01.472 INFO [stdout] running 0 tests
Nov 17 05:51:01.472 INFO [stdout] 
Nov 17 05:51:01.472 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 17 05:51:01.472 INFO [stdout] 
Nov 17 05:51:01.479 INFO [stderr]      Running /target/debug/deps/lib-8ada69a293c6ae9a
Nov 17 05:51:01.481 INFO [stdout] 
Nov 17 05:51:01.481 INFO [stdout] running 29 tests
Nov 17 05:51:01.521 INFO [stdout] test serde_round_trip_bool ... ok
Nov 17 05:51:01.527 INFO [stdout] test serde_round_trip_f64 ... ok
Nov 17 05:51:01.535 INFO [stdout] test serde_round_trip_bytes ... ok
Nov 17 05:51:01.563 INFO [stdout] test serde_round_trip_named_struct ... ok
Nov 17 05:51:01.572 INFO [stdout] test serde_round_trip_isize ... ok
Nov 17 05:51:01.577 INFO [stdout] test serde_round_trip_newtype_struct ... ok
Nov 17 05:51:01.607 INFO [stdout] test serde_round_trip_option_point ... ok
Nov 17 05:51:01.607 INFO [stdout] test serde_round_trip_option_u64 ... ok
Nov 17 05:51:01.623 INFO [stdout] test serde_round_trip_someenum ... ok
Nov 17 05:51:01.639 INFO [stdout] test serde_round_trip_option_string ... ok
Nov 17 05:51:01.687 INFO [stdout] test serde_round_trip_struct_tuple ... ok
Nov 17 05:51:01.687 INFO [stdout] test serde_round_trip_onetuple_named_struct ... ok
Nov 17 05:51:01.727 INFO [stdout] test serde_round_trip_tuple_u64 ... ok
Nov 17 05:51:01.727 INFO [stdout] test serde_round_trip_tuple_u64_u64 ... ok
Nov 17 05:51:01.739 INFO [stdout] test serde_round_trip_string ... ok
Nov 17 05:51:01.750 INFO [stdout] test serde_round_trip_tuple_u64_u64_u64 ... ok
Nov 17 05:51:01.759 INFO [stdout] test serde_round_trip_u8 ... ok
Nov 17 05:51:01.759 INFO [stdout] test serde_round_trip_unit ... ok
Nov 17 05:51:01.760 INFO [stdout] test serde_round_trip_u64 ... ok
Nov 17 05:51:01.767 INFO [stdout] test serde_round_trip_unity_struct ... ok
Nov 17 05:51:01.831 INFO [stdout] test serde_round_trip_tuple_string_u64 ... ok
Nov 17 05:51:01.832 INFO [stdout] test test_bytes_repr ... ok
Nov 17 05:51:01.896 INFO [stdout] test serde_round_trip_incremental_framing_atom ... ok
Nov 17 05:51:01.897 INFO [stdout] test serde_round_trip_vec_u64 ... ok
Nov 17 05:51:01.960 INFO [stdout] test serde_round_trip_incremental_option_u64 ... ok
Nov 17 05:51:02.091 INFO [stdout] test serde_round_trip_incremental_framing ... ok
Nov 17 05:51:02.091 INFO [stdout] test serde_round_trip_map_u64_u64 ... ok
Nov 17 05:51:02.095 INFO [stdout] test round_trip_tokens ... ok
Nov 17 05:51:02.464 INFO [stdout] test serde_round_trip_vec_string ... ok
Nov 17 05:51:02.465 INFO [stdout] 
Nov 17 05:51:02.465 INFO [stdout] test result: ok. 29 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 17 05:51:02.465 INFO [stdout] 
Nov 17 05:51:02.467 INFO [stderr]    Doc-tests spki-sexp
Nov 17 05:51:03.475 INFO [stdout] 
Nov 17 05:51:03.475 INFO [stdout] running 0 tests
Nov 17 05:51:03.475 INFO [stdout] 
Nov 17 05:51:03.475 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 17 05:51:03.475 INFO [stdout] 
Nov 17 05:51:03.479 INFO [stderr] su: No module specific data is present
Nov 17 05:51:03.981 INFO running `"docker" "inspect" "ead584bed598d57c8cdb875dd1add4fbab57c777f629ce5361deb8a46e62ee22"`
Nov 17 05:51:04.059 INFO running `"docker" "rm" "-f" "ead584bed598d57c8cdb875dd1add4fbab57c777f629ce5361deb8a46e62ee22"`
Nov 17 05:51:04.373 INFO [stdout] ead584bed598d57c8cdb875dd1add4fbab57c777f629ce5361deb8a46e62ee22