[INFO] crate multipart 0.16.1 is already in cache [INFO] extracting crate multipart 0.16.1 into work/ex/beta-1.37-6/sources/1.36.0/reg/multipart/0.16.1 [INFO] extracting crate multipart 0.16.1 into work/ex/beta-1.37-6/sources/beta-2019-07-23/reg/multipart/0.16.1 [INFO] validating manifest of multipart-0.16.1 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 multipart-0.16.1 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 multipart-0.16.1 [INFO] removed 8 missing examples [INFO] finished frobbing multipart-0.16.1 [INFO] frobbed toml for multipart-0.16.1 written to work/ex/beta-1.37-6/sources/1.36.0/reg/multipart/0.16.1/Cargo.toml [INFO] started frobbing multipart-0.16.1 [INFO] removed 8 missing examples [INFO] finished frobbing multipart-0.16.1 [INFO] frobbed toml for multipart-0.16.1 written to work/ex/beta-1.37-6/sources/beta-2019-07-23/reg/multipart/0.16.1/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 multipart-0.16.1 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-5/1.36.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.37-6/sources/1.36.0/reg/multipart/0.16.1:/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] f039e4dc61711972c0666d7075165e8516114f3faccfdee4b7b36bbf9c1d50a8 [INFO] running `"docker" "start" "-a" "f039e4dc61711972c0666d7075165e8516114f3faccfdee4b7b36bbf9c1d50a8"` [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/read_file.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] warning: An explicit [[example]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other example targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a example target: [INFO] [stderr] [INFO] [stderr] * /opt/crater/workdir/examples/hyper_client.rs [INFO] [stderr] * /opt/crater/workdir/examples/nickel.rs [INFO] [stderr] * /opt/crater/workdir/examples/iron_intercept.rs [INFO] [stderr] * /opt/crater/workdir/examples/rocket.rs [INFO] [stderr] * /opt/crater/workdir/examples/hyper_reqbuilder.rs [INFO] [stderr] * /opt/crater/workdir/examples/tiny_http.rs [INFO] [stderr] * /opt/crater/workdir/examples/iron.rs [INFO] [stderr] * /opt/crater/workdir/examples/hyper_server.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 example target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autoexamples = 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 mustache v0.9.0 [INFO] [stderr] Compiling nickel v0.11.0 [INFO] [stderr] Compiling multipart v0.16.1 (/opt/crater/workdir) [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 13.27s [INFO] running `"docker" "inspect" "f039e4dc61711972c0666d7075165e8516114f3faccfdee4b7b36bbf9c1d50a8"` [INFO] running `"docker" "rm" "-f" "f039e4dc61711972c0666d7075165e8516114f3faccfdee4b7b36bbf9c1d50a8"` [INFO] [stdout] f039e4dc61711972c0666d7075165e8516114f3faccfdee4b7b36bbf9c1d50a8 [INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.37-6/worker-5/1.36.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.37-6/sources/1.36.0/reg/multipart/0.16.1:/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] 97e601b3a1b642da209a9a1f61db0f19ea0ef4ceb47784104fdf5db47220ae0c [INFO] running `"docker" "start" "-a" "97e601b3a1b642da209a9a1f61db0f19ea0ef4ceb47784104fdf5db47220ae0c"` [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/read_file.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] warning: An explicit [[example]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other example targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a example target: [INFO] [stderr] [INFO] [stderr] * /opt/crater/workdir/examples/hyper_client.rs [INFO] [stderr] * /opt/crater/workdir/examples/nickel.rs [INFO] [stderr] * /opt/crater/workdir/examples/iron_intercept.rs [INFO] [stderr] * /opt/crater/workdir/examples/rocket.rs [INFO] [stderr] * /opt/crater/workdir/examples/hyper_reqbuilder.rs [INFO] [stderr] * /opt/crater/workdir/examples/tiny_http.rs [INFO] [stderr] * /opt/crater/workdir/examples/iron.rs [INFO] [stderr] * /opt/crater/workdir/examples/hyper_server.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 example target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autoexamples = 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 multipart v0.16.1 (/opt/crater/workdir) [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 6.80s [INFO] running `"docker" "inspect" "97e601b3a1b642da209a9a1f61db0f19ea0ef4ceb47784104fdf5db47220ae0c"` [INFO] running `"docker" "rm" "-f" "97e601b3a1b642da209a9a1f61db0f19ea0ef4ceb47784104fdf5db47220ae0c"` [INFO] [stdout] 97e601b3a1b642da209a9a1f61db0f19ea0ef4ceb47784104fdf5db47220ae0c [INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.37-6/worker-5/1.36.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.37-6/sources/1.36.0/reg/multipart/0.16.1:/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] b24968bccf7fc003663bb7a25530848ccd727d2cc2182fcebffb9a574de7cc17 [INFO] running `"docker" "start" "-a" "b24968bccf7fc003663bb7a25530848ccd727d2cc2182fcebffb9a574de7cc17"` [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/read_file.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] warning: An explicit [[example]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other example targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a example target: [INFO] [stderr] [INFO] [stderr] * /opt/crater/workdir/examples/hyper_client.rs [INFO] [stderr] * /opt/crater/workdir/examples/nickel.rs [INFO] [stderr] * /opt/crater/workdir/examples/iron_intercept.rs [INFO] [stderr] * /opt/crater/workdir/examples/rocket.rs [INFO] [stderr] * /opt/crater/workdir/examples/hyper_reqbuilder.rs [INFO] [stderr] * /opt/crater/workdir/examples/tiny_http.rs [INFO] [stderr] * /opt/crater/workdir/examples/iron.rs [INFO] [stderr] * /opt/crater/workdir/examples/hyper_server.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 example target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autoexamples = 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.09s [INFO] [stderr] Running /opt/crater/target/debug/deps/multipart-d04deadb12d1e448 [INFO] [stdout] [INFO] [stdout] running 21 tests [INFO] [stdout] test local_test::extended::lazy_client_entry_server ... ignored [INFO] [stdout] test local_test::extended::lazy_client_reg_server ... ignored [INFO] [stdout] test local_test::extended::reg_client_entry_server ... ignored [INFO] [stdout] test local_test::extended::reg_client_reg_server ... ignored [INFO] [stdout] test local_test::lazy_client_entry_server ... ok [INFO] [stdout] test local_test::lazy_client_reg_server ... ok [INFO] [stdout] test local_test::reg_client_reg_server ... ok [INFO] [stdout] test local_test::reg_client_entry_server ... ok [INFO] [stdout] test server::boundary::test::test_boundary ... ok [INFO] [stdout] test server::boundary::test::test_empty_body ... ok [INFO] [stdout] test server::boundary::test::test_leading_crlf ... ok [INFO] [stdout] test server::boundary::test::test_invalid_boundary ... ok [INFO] [stdout] test server::boundary::test::test_lone_boundary ... ok [INFO] [stdout] test server::boundary::test::test_skip_field ... ok [INFO] [stdout] test server::boundary::test::test_trailing_lflf ... ok [INFO] [stdout] test server::field::test_find_header ... ok [INFO] [stdout] test server::boundary::test::test_split_boundary ... ok [INFO] [stdout] test server::boundary::test::test_trailing_crlf ... ok [INFO] [stdout] test server::boundary::test::test_unterminated_body ... ok [INFO] [stdout] test server::issue_114 ... ok [INFO] [stdout] test server::issue_104 ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 17 passed; 0 failed; 4 ignored; 0 measured; 0 filtered out [INFO] [stdout] [INFO] [stderr] Running /opt/crater/target/debug/deps/form_test-2458a4e5a1192b29 [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] [stderr] Doc-tests multipart [INFO] [stdout] [INFO] [stdout] running 2 tests [INFO] [stdout] test src/server/iron.rs - server::iron::Intercept (line 49) ... ok [INFO] [stdout] test src/lib.rs - chain_result (line 80) ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out [INFO] [stdout] [INFO] running `"docker" "inspect" "b24968bccf7fc003663bb7a25530848ccd727d2cc2182fcebffb9a574de7cc17"` [INFO] running `"docker" "rm" "-f" "b24968bccf7fc003663bb7a25530848ccd727d2cc2182fcebffb9a574de7cc17"` [INFO] [stdout] b24968bccf7fc003663bb7a25530848ccd727d2cc2182fcebffb9a574de7cc17