Dec 13 08:22:04.592 INFO testing okanon/rthrift_tutorial against try#aa49d8ef14939ddec0e34b346b60174a5673d48f for pr-56550 Dec 13 08:22:04.592 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-5/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/pr-56550/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/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 +aa49d8ef14939ddec0e34b346b60174a5673d48f-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"` Dec 13 08:22:05.143 INFO [stdout] 5770ab6b79ade5941fbd45e478d00ce1479e957ef2b112f80499d0954e409cec Dec 13 08:22:05.148 INFO running `"docker" "start" "-a" "5770ab6b79ade5941fbd45e478d00ce1479e957ef2b112f80499d0954e409cec"` Dec 13 08:22:06.362 INFO [stderr] usermod: no changes Dec 13 08:22:06.399 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 13 08:22:06.399 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 13 08:22:06.399 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 13 08:22:06.399 INFO [stderr] files will be included as a binary target: Dec 13 08:22:06.399 INFO [stderr] Dec 13 08:22:06.399 INFO [stderr] * /source/src/main.rs Dec 13 08:22:06.399 INFO [stderr] Dec 13 08:22:06.399 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 13 08:22:06.399 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 13 08:22:06.399 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 13 08:22:06.399 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 13 08:22:06.399 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 13 08:22:06.399 INFO [stderr] Dec 13 08:22:06.399 INFO [stderr] For more information on this warning you can consult Dec 13 08:22:06.399 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 13 08:22:06.446 INFO [stderr] Compiling try_from v0.2.2 Dec 13 08:22:06.446 INFO [stderr] Compiling integer-encoding v1.0.5 Dec 13 08:22:06.447 INFO [stderr] Compiling threadpool v1.7.1 Dec 13 08:22:06.451 INFO [stderr] Compiling clap v2.27.1 Dec 13 08:22:06.451 INFO [stderr] Compiling ordered-float v0.3.0 Dec 13 08:22:08.599 INFO [stderr] Compiling rthrift v0.11.0 Dec 13 08:22:32.591 INFO [stderr] Compiling rthrift_tutorial v0.1.0 (/source) Dec 13 08:22:37.091 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 30.70s Dec 13 08:22:37.097 INFO [stderr] su: No module specific data is present Dec 13 08:22:37.755 INFO running `"docker" "inspect" "5770ab6b79ade5941fbd45e478d00ce1479e957ef2b112f80499d0954e409cec"` Dec 13 08:22:38.060 INFO running `"docker" "rm" "-f" "5770ab6b79ade5941fbd45e478d00ce1479e957ef2b112f80499d0954e409cec"` Dec 13 08:22:38.411 INFO [stdout] 5770ab6b79ade5941fbd45e478d00ce1479e957ef2b112f80499d0954e409cec Dec 13 08:22:38.419 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-5/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/pr-56550/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/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 +aa49d8ef14939ddec0e34b346b60174a5673d48f-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"` Dec 13 08:22:38.946 INFO [stdout] b8cc042fbfdce2e110171bacfa54acb21a9ad64374658a0c9a2da5a2236016d3 Dec 13 08:22:38.948 INFO running `"docker" "start" "-a" "b8cc042fbfdce2e110171bacfa54acb21a9ad64374658a0c9a2da5a2236016d3"` Dec 13 08:22:41.654 INFO [stderr] usermod: no changes Dec 13 08:22:41.727 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 13 08:22:41.728 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 13 08:22:41.728 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 13 08:22:41.728 INFO [stderr] files will be included as a binary target: Dec 13 08:22:41.728 INFO [stderr] Dec 13 08:22:41.728 INFO [stderr] * /source/src/main.rs Dec 13 08:22:41.728 INFO [stderr] Dec 13 08:22:41.728 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 13 08:22:41.728 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 13 08:22:41.728 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 13 08:22:41.728 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 13 08:22:41.728 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 13 08:22:41.728 INFO [stderr] Dec 13 08:22:41.728 INFO [stderr] For more information on this warning you can consult Dec 13 08:22:41.728 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 13 08:22:41.828 INFO [stderr] Compiling rthrift_tutorial v0.1.0 (/source) Dec 13 08:22:44.552 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 2.88s Dec 13 08:22:44.557 INFO [stderr] su: No module specific data is present Dec 13 08:22:45.807 INFO running `"docker" "inspect" "b8cc042fbfdce2e110171bacfa54acb21a9ad64374658a0c9a2da5a2236016d3"` Dec 13 08:22:46.135 INFO running `"docker" "rm" "-f" "b8cc042fbfdce2e110171bacfa54acb21a9ad64374658a0c9a2da5a2236016d3"` Dec 13 08:22:46.491 INFO [stdout] b8cc042fbfdce2e110171bacfa54acb21a9ad64374658a0c9a2da5a2236016d3 Dec 13 08:22:46.496 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-5/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/pr-56550/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/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 +aa49d8ef14939ddec0e34b346b60174a5673d48f-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"` Dec 13 08:22:47.072 INFO [stdout] 6853e5684c92c276affa89fa29a3ef4bf64357eb1b017e5ddcfe971358fe3210 Dec 13 08:22:47.074 INFO running `"docker" "start" "-a" "6853e5684c92c276affa89fa29a3ef4bf64357eb1b017e5ddcfe971358fe3210"` Dec 13 08:22:48.836 INFO [stderr] usermod: no changes Dec 13 08:22:48.907 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 13 08:22:48.907 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 13 08:22:48.907 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 13 08:22:48.907 INFO [stderr] files will be included as a binary target: Dec 13 08:22:48.907 INFO [stderr] Dec 13 08:22:48.907 INFO [stderr] * /source/src/main.rs Dec 13 08:22:48.907 INFO [stderr] Dec 13 08:22:48.907 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 13 08:22:48.907 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 13 08:22:48.907 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 13 08:22:48.907 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 13 08:22:48.907 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 13 08:22:48.907 INFO [stderr] Dec 13 08:22:48.907 INFO [stderr] For more information on this warning you can consult Dec 13 08:22:48.907 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 13 08:22:48.935 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.06s Dec 13 08:22:48.943 INFO [stderr] Running /target/debug/deps/rthrift_tutorial-119e23dcd31d9581 Dec 13 08:22:48.951 INFO [stderr] Running /target/debug/deps/rthrift_tutorial_client-79753a5771cf6b57 Dec 13 08:22:48.951 INFO [stdout] Dec 13 08:22:48.951 INFO [stderr] Running /target/debug/deps/rthrift_tutorial_server-b83ae5683d90aa36 Dec 13 08:22:48.951 INFO [stdout] running 0 tests Dec 13 08:22:48.951 INFO [stderr] Doc-tests rthrift_tutorial Dec 13 08:22:48.951 INFO [stdout] Dec 13 08:22:48.951 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 13 08:22:48.951 INFO [stdout] Dec 13 08:22:48.951 INFO [stdout] Dec 13 08:22:48.951 INFO [stdout] running 0 tests Dec 13 08:22:48.951 INFO [stdout] Dec 13 08:22:48.951 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 13 08:22:48.951 INFO [stdout] Dec 13 08:22:48.951 INFO [stdout] Dec 13 08:22:48.951 INFO [stdout] running 0 tests Dec 13 08:22:48.951 INFO [stdout] Dec 13 08:22:48.951 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 13 08:22:48.951 INFO [stdout] Dec 13 08:22:49.759 INFO [stdout] Dec 13 08:22:49.759 INFO [stdout] running 0 tests Dec 13 08:22:49.759 INFO [stdout] Dec 13 08:22:49.759 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 13 08:22:49.759 INFO [stdout] Dec 13 08:22:49.767 INFO [stderr] su: No module specific data is present Dec 13 08:22:50.523 INFO running `"docker" "inspect" "6853e5684c92c276affa89fa29a3ef4bf64357eb1b017e5ddcfe971358fe3210"` Dec 13 08:22:50.935 INFO running `"docker" "rm" "-f" "6853e5684c92c276affa89fa29a3ef4bf64357eb1b017e5ddcfe971358fe3210"` Dec 13 08:22:51.253 INFO [stdout] 6853e5684c92c276affa89fa29a3ef4bf64357eb1b017e5ddcfe971358fe3210