[INFO] crate multipart 0.16.1 is already in cache [INFO] testing multipart-0.16.1 against beta-2019-09-28 for beta-1.39-1 [INFO] extracting crate multipart 0.16.1 into work/builds/worker-2/source [INFO] validating manifest of crates.io crate multipart 0.16.1 on toolchain beta-2019-09-28 [INFO] running `"/big/crater/work/cargo-home/bin/cargo" "+beta-2019-09-28" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] started tweaking crates.io crate multipart 0.16.1 [INFO] removed 8 missing examples [INFO] finished tweaking crates.io crate multipart 0.16.1 [INFO] tweaked toml for crates.io crate multipart 0.16.1 written to work/builds/worker-2/source/Cargo.toml [INFO] running `"/big/crater/work/cargo-home/bin/cargo" "+beta-2019-09-28" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/big/crater/work/cargo-home/bin/cargo" "+beta-2019-09-28" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [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] * /big/crater/work/builds/worker-2/source/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] * /big/crater/work/builds/worker-2/source/examples/iron_intercept.rs [INFO] [stderr] * /big/crater/work/builds/worker-2/source/examples/hyper_client.rs [INFO] [stderr] * /big/crater/work/builds/worker-2/source/examples/hyper_server.rs [INFO] [stderr] * /big/crater/work/builds/worker-2/source/examples/tiny_http.rs [INFO] [stderr] * /big/crater/work/builds/worker-2/source/examples/iron.rs [INFO] [stderr] * /big/crater/work/builds/worker-2/source/examples/rocket.rs [INFO] [stderr] * /big/crater/work/builds/worker-2/source/examples/hyper_reqbuilder.rs [INFO] [stderr] * /big/crater/work/builds/worker-2/source/examples/nickel.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] running `"docker" "create" "-v" "/big/crater/work/builds/worker-2/target:/opt/rustwide/target:rw,Z" "-v" "/big/crater/work/builds/worker-2/source:/opt/rustwide/workdir:ro,Z" "-v" "/big/crater/work/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/big/crater/work/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--network" "none" "rustops/crates-build-env" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2019-09-28" "build" "--frozen"` [INFO] [stdout] 9f404ce5cc6a0378c52b8fbcd2594b33842cb12983a965f302a8003e7cadb820 [INFO] running `"docker" "start" "-a" "9f404ce5cc6a0378c52b8fbcd2594b33842cb12983a965f302a8003e7cadb820"` [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/rustwide/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/rustwide/workdir/examples/iron_intercept.rs [INFO] [stderr] * /opt/rustwide/workdir/examples/hyper_client.rs [INFO] [stderr] * /opt/rustwide/workdir/examples/hyper_server.rs [INFO] [stderr] * /opt/rustwide/workdir/examples/tiny_http.rs [INFO] [stderr] * /opt/rustwide/workdir/examples/iron.rs [INFO] [stderr] * /opt/rustwide/workdir/examples/rocket.rs [INFO] [stderr] * /opt/rustwide/workdir/examples/hyper_reqbuilder.rs [INFO] [stderr] * /opt/rustwide/workdir/examples/nickel.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 chunked_transfer v0.3.1 [INFO] [stderr] Compiling ascii v0.8.7 [INFO] [stderr] Compiling buf_redux v0.8.4 [INFO] [stderr] Compiling twoway v0.1.8 [INFO] [stderr] Compiling nickel v0.11.0 [INFO] [stderr] Compiling tiny_http v0.6.2 [INFO] [stderr] Compiling multipart v0.16.1 (/opt/rustwide/workdir) [INFO] [stderr] warning: trait objects without an explicit `dyn` are deprecated [INFO] [stderr] --> src/client/lazy.rs:86:32 [INFO] [stderr] | [INFO] [stderr] 86 | fn cause(&self) -> Option<&Error> { [INFO] [stderr] | ^^^^^ help: use `dyn`: `dyn Error` [INFO] [stderr] | [INFO] [stderr] = note: `#[warn(bare_trait_objects)]` on by default [INFO] [stderr] [INFO] [stderr] warning: trait objects without an explicit `dyn` are deprecated [INFO] [stderr] --> src/client/lazy.rs:222:17 [INFO] [stderr] | [INFO] [stderr] 222 | stream: Box, [INFO] [stderr] | ^^^^^^^^^ help: use `dyn`: `dyn Read + 'd` [INFO] [stderr] [INFO] [stderr] warning: trait objects without an explicit `dyn` are deprecated [INFO] [stderr] --> src/client/lazy.rs:340:17 [INFO] [stderr] | [INFO] [stderr] 340 | stream: Box, [INFO] [stderr] | ^^^^^^^^^ help: use `dyn`: `dyn Read + 'd` [INFO] [stderr] [INFO] [stderr] warning: trait objects without an explicit `dyn` are deprecated [INFO] [stderr] --> src/client/lazy.rs:357:105 [INFO] [stderr] | [INFO] [stderr] 357 | fn from_stream(name: &str, boundary: &str, content_type: &Mime, filename: Option<&str>, stream: Box) -> Self { [INFO] [stderr] | ^^^^^^^^^ help: use `dyn`: `dyn Read + 'd` [INFO] [stderr] [INFO] [stderr] warning: trait objects without an explicit `dyn` are deprecated [INFO] [stderr] --> src/server/tiny_http.rs:14:25 [INFO] [stderr] | [INFO] [stderr] 14 | type Body = &'r mut Read; [INFO] [stderr] | ^^^^ help: use `dyn`: `dyn Read` [INFO] [stderr] [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 12.87s [INFO] running `"docker" "inspect" "9f404ce5cc6a0378c52b8fbcd2594b33842cb12983a965f302a8003e7cadb820"` [INFO] running `"docker" "rm" "-f" "9f404ce5cc6a0378c52b8fbcd2594b33842cb12983a965f302a8003e7cadb820"` [INFO] [stdout] 9f404ce5cc6a0378c52b8fbcd2594b33842cb12983a965f302a8003e7cadb820 [INFO] running `"docker" "create" "-v" "/big/crater/work/builds/worker-2/target:/opt/rustwide/target:rw,Z" "-v" "/big/crater/work/builds/worker-2/source:/opt/rustwide/workdir:ro,Z" "-v" "/big/crater/work/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/big/crater/work/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--network" "none" "rustops/crates-build-env" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2019-09-28" "test" "--frozen" "--no-run"` [INFO] [stdout] a566b90602973014414907d49c3884dd5ed8d767d2586f3c08964c219854541c [INFO] running `"docker" "start" "-a" "a566b90602973014414907d49c3884dd5ed8d767d2586f3c08964c219854541c"` [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/rustwide/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/rustwide/workdir/examples/iron_intercept.rs [INFO] [stderr] * /opt/rustwide/workdir/examples/hyper_client.rs [INFO] [stderr] * /opt/rustwide/workdir/examples/hyper_server.rs [INFO] [stderr] * /opt/rustwide/workdir/examples/tiny_http.rs [INFO] [stderr] * /opt/rustwide/workdir/examples/iron.rs [INFO] [stderr] * /opt/rustwide/workdir/examples/rocket.rs [INFO] [stderr] * /opt/rustwide/workdir/examples/hyper_reqbuilder.rs [INFO] [stderr] * /opt/rustwide/workdir/examples/nickel.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/rustwide/workdir) [INFO] [stderr] warning: trait objects without an explicit `dyn` are deprecated [INFO] [stderr] --> src/client/lazy.rs:86:32 [INFO] [stderr] | [INFO] [stderr] 86 | fn cause(&self) -> Option<&Error> { [INFO] [stderr] | ^^^^^ help: use `dyn`: `dyn Error` [INFO] [stderr] | [INFO] [stderr] = note: `#[warn(bare_trait_objects)]` on by default [INFO] [stderr] [INFO] [stderr] warning: trait objects without an explicit `dyn` are deprecated [INFO] [stderr] --> src/client/lazy.rs:222:17 [INFO] [stderr] | [INFO] [stderr] 222 | stream: Box, [INFO] [stderr] | ^^^^^^^^^ help: use `dyn`: `dyn Read + 'd` [INFO] [stderr] [INFO] [stderr] warning: trait objects without an explicit `dyn` are deprecated [INFO] [stderr] --> src/client/lazy.rs:340:17 [INFO] [stderr] | [INFO] [stderr] 340 | stream: Box, [INFO] [stderr] | ^^^^^^^^^ help: use `dyn`: `dyn Read + 'd` [INFO] [stderr] [INFO] [stderr] warning: trait objects without an explicit `dyn` are deprecated [INFO] [stderr] --> src/client/lazy.rs:357:105 [INFO] [stderr] | [INFO] [stderr] 357 | fn from_stream(name: &str, boundary: &str, content_type: &Mime, filename: Option<&str>, stream: Box) -> Self { [INFO] [stderr] | ^^^^^^^^^ help: use `dyn`: `dyn Read + 'd` [INFO] [stderr] [INFO] [stderr] warning: trait objects without an explicit `dyn` are deprecated [INFO] [stderr] --> src/server/tiny_http.rs:14:25 [INFO] [stderr] | [INFO] [stderr] 14 | type Body = &'r mut Read; [INFO] [stderr] | ^^^^ help: use `dyn`: `dyn Read` [INFO] [stderr] [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 9.01s [INFO] running `"docker" "inspect" "a566b90602973014414907d49c3884dd5ed8d767d2586f3c08964c219854541c"` [INFO] running `"docker" "rm" "-f" "a566b90602973014414907d49c3884dd5ed8d767d2586f3c08964c219854541c"` [INFO] [stdout] a566b90602973014414907d49c3884dd5ed8d767d2586f3c08964c219854541c [INFO] running `"docker" "create" "-v" "/big/crater/work/builds/worker-2/target:/opt/rustwide/target:rw,Z" "-v" "/big/crater/work/builds/worker-2/source:/opt/rustwide/workdir:ro,Z" "-v" "/big/crater/work/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/big/crater/work/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--network" "none" "rustops/crates-build-env" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2019-09-28" "test" "--frozen"` [INFO] [stdout] 8bcc280e6aed256312a89bd7f1d3e7b33c08346535f0350cf33233a3ce6956f4 [INFO] running `"docker" "start" "-a" "8bcc280e6aed256312a89bd7f1d3e7b33c08346535f0350cf33233a3ce6956f4"` [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/rustwide/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/rustwide/workdir/examples/iron_intercept.rs [INFO] [stderr] * /opt/rustwide/workdir/examples/hyper_client.rs [INFO] [stderr] * /opt/rustwide/workdir/examples/hyper_server.rs [INFO] [stderr] * /opt/rustwide/workdir/examples/tiny_http.rs [INFO] [stderr] * /opt/rustwide/workdir/examples/iron.rs [INFO] [stderr] * /opt/rustwide/workdir/examples/rocket.rs [INFO] [stderr] * /opt/rustwide/workdir/examples/hyper_reqbuilder.rs [INFO] [stderr] * /opt/rustwide/workdir/examples/nickel.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.54s [INFO] [stderr] Running /opt/rustwide/target/debug/deps/multipart-ac1cf5d1b34f23d0 [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 server::boundary::test::test_empty_body ... ok [INFO] [stdout] test server::boundary::test::test_boundary ... ok [INFO] [stdout] test server::boundary::test::test_invalid_boundary ... ok [INFO] [stdout] test server::boundary::test::test_skip_field ... ok [INFO] [stdout] test server::boundary::test::test_leading_crlf ... ok [INFO] [stdout] test server::boundary::test::test_trailing_crlf ... ok [INFO] [stdout] test local_test::lazy_client_entry_server ... ok [INFO] [stdout] test local_test::reg_client_entry_server ... ok [INFO] [stdout] test server::field::test_find_header ... ok [INFO] [stdout] test server::boundary::test::test_trailing_lflf ... ok [INFO] [stdout] test server::issue_104 ... ok [INFO] [stdout] test server::boundary::test::test_unterminated_body ... ok [INFO] [stdout] test local_test::lazy_client_reg_server ... ok [INFO] [stdout] test local_test::reg_client_reg_server ... ok [INFO] [stdout] test server::boundary::test::test_lone_boundary ... ok [INFO] [stdout] test server::boundary::test::test_split_boundary ... ok [INFO] [stdout] test server::issue_114 ... 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/rustwide/target/debug/deps/form_test-589859d5a8c657a8 [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" "8bcc280e6aed256312a89bd7f1d3e7b33c08346535f0350cf33233a3ce6956f4"` [INFO] running `"docker" "rm" "-f" "8bcc280e6aed256312a89bd7f1d3e7b33c08346535f0350cf33233a3ce6956f4"` [INFO] [stdout] 8bcc280e6aed256312a89bd7f1d3e7b33c08346535f0350cf33233a3ce6956f4