Dec 01 16:50:05.492 INFO testing gellati/rust-examples against 1.30.1 for beta-1.31-5
Dec 01 16:50:05.492 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-5/1.30.1:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/beta-1.31-5/1.30.1:/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 +1.30.1 build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 01 16:50:05.884 INFO [stdout] eac2b6b6a5257bd55d08b0b37e323a19ffb8b4da60ef235f800e9a6df0463eb5
Dec 01 16:50:05.887 INFO running `"docker" "start" "-a" "eac2b6b6a5257bd55d08b0b37e323a19ffb8b4da60ef235f800e9a6df0463eb5"`
Dec 01 16:50:07.870 INFO [stderr] usermod: no changes
Dec 01 16:50:07.931 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 01 16:50:07.931 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 01 16:50:07.931 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 01 16:50:07.931 INFO [stderr] files will be included as a binary target:
Dec 01 16:50:07.931 INFO [stderr] 
Dec 01 16:50:07.931 INFO [stderr] * /source/src/main.rs
Dec 01 16:50:07.931 INFO [stderr] 
Dec 01 16:50:07.931 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 01 16:50:07.931 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 01 16:50:07.931 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 01 16:50:07.931 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 01 16:50:07.931 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 01 16:50:07.931 INFO [stderr] 
Dec 01 16:50:07.931 INFO [stderr] For more information on this warning you can consult
Dec 01 16:50:07.931 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 01 16:50:07.931 INFO [stderr]    Compiling rust-basics v0.1.0 (/source)
Dec 01 16:50:09.553 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.64s
Dec 01 16:50:09.563 INFO [stderr] su: No module specific data is present
Dec 01 16:50:10.287 INFO running `"docker" "inspect" "eac2b6b6a5257bd55d08b0b37e323a19ffb8b4da60ef235f800e9a6df0463eb5"`
Dec 01 16:50:10.568 INFO running `"docker" "rm" "-f" "eac2b6b6a5257bd55d08b0b37e323a19ffb8b4da60ef235f800e9a6df0463eb5"`
Dec 01 16:50:10.878 INFO [stdout] eac2b6b6a5257bd55d08b0b37e323a19ffb8b4da60ef235f800e9a6df0463eb5
Dec 01 16:50:10.881 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-5/1.30.1:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/beta-1.31-5/1.30.1:/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 +1.30.1 test --frozen --no-run" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 01 16:50:11.315 INFO [stdout] 0dc94a108879e771ffc53343a093d4dad9dc1ee3677e6efe11cd92ccb7c02cff
Dec 01 16:50:11.323 INFO running `"docker" "start" "-a" "0dc94a108879e771ffc53343a093d4dad9dc1ee3677e6efe11cd92ccb7c02cff"`
Dec 01 16:50:12.703 INFO [stderr] usermod: no changes
Dec 01 16:50:12.771 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 01 16:50:12.771 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 01 16:50:12.771 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 01 16:50:12.771 INFO [stderr] files will be included as a binary target:
Dec 01 16:50:12.771 INFO [stderr] 
Dec 01 16:50:12.771 INFO [stderr] * /source/src/main.rs
Dec 01 16:50:12.771 INFO [stderr] 
Dec 01 16:50:12.771 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 01 16:50:12.771 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 01 16:50:12.771 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 01 16:50:12.771 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 01 16:50:12.771 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 01 16:50:12.771 INFO [stderr] 
Dec 01 16:50:12.771 INFO [stderr] For more information on this warning you can consult
Dec 01 16:50:12.771 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 01 16:50:12.779 INFO [stderr]    Compiling rust-basics v0.1.0 (/source)
Dec 01 16:50:14.754 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.00s
Dec 01 16:50:14.767 INFO [stderr] su: No module specific data is present
Dec 01 16:50:15.651 INFO running `"docker" "inspect" "0dc94a108879e771ffc53343a093d4dad9dc1ee3677e6efe11cd92ccb7c02cff"`
Dec 01 16:50:15.964 INFO running `"docker" "rm" "-f" "0dc94a108879e771ffc53343a093d4dad9dc1ee3677e6efe11cd92ccb7c02cff"`
Dec 01 16:50:16.319 INFO [stdout] 0dc94a108879e771ffc53343a093d4dad9dc1ee3677e6efe11cd92ccb7c02cff
Dec 01 16:50:16.327 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-5/1.30.1:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/beta-1.31-5/1.30.1:/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 +1.30.1 test --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 01 16:50:16.784 INFO [stdout] d371e7a6d7d4e39ae064bad677ed6717d98f5b83aca161189be7261d8efaf760
Dec 01 16:50:16.787 INFO running `"docker" "start" "-a" "d371e7a6d7d4e39ae064bad677ed6717d98f5b83aca161189be7261d8efaf760"`
Dec 01 16:50:18.138 INFO [stderr] usermod: no changes
Dec 01 16:50:18.167 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 01 16:50:18.167 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 01 16:50:18.167 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 01 16:50:18.167 INFO [stderr] files will be included as a binary target:
Dec 01 16:50:18.167 INFO [stderr] 
Dec 01 16:50:18.167 INFO [stderr] * /source/src/main.rs
Dec 01 16:50:18.167 INFO [stderr] 
Dec 01 16:50:18.167 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 01 16:50:18.167 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 01 16:50:18.167 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 01 16:50:18.167 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 01 16:50:18.167 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 01 16:50:18.167 INFO [stderr] 
Dec 01 16:50:18.167 INFO [stderr] For more information on this warning you can consult
Dec 01 16:50:18.167 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 01 16:50:18.167 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.01s
Dec 01 16:50:18.169 INFO [stderr]      Running /target/debug/deps/attribute-777dd671c60a01d2
Dec 01 16:50:18.175 INFO [stderr]      Running /target/debug/deps/box-33d10ab9eb2b3c03
Dec 01 16:50:18.175 INFO [stdout] 
Dec 01 16:50:18.175 INFO [stdout] running 0 tests
Dec 01 16:50:18.175 INFO [stdout] 
Dec 01 16:50:18.175 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 01 16:50:18.175 INFO [stdout] 
Dec 01 16:50:18.176 INFO [stdout] 
Dec 01 16:50:18.176 INFO [stderr]      Running /target/debug/deps/generic-509ce102cb56cb49
Dec 01 16:50:18.176 INFO [stdout] running 0 tests
Dec 01 16:50:18.176 INFO [stdout] 
Dec 01 16:50:18.176 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 01 16:50:18.176 INFO [stdout] 
Dec 01 16:50:18.177 INFO [stdout] 
Dec 01 16:50:18.177 INFO [stdout] running 0 tests
Dec 01 16:50:18.177 INFO [stdout] 
Dec 01 16:50:18.177 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 01 16:50:18.177 INFO [stdout] 
Dec 01 16:50:18.179 INFO [stderr] su: No module specific data is present
Dec 01 16:50:18.613 INFO running `"docker" "inspect" "d371e7a6d7d4e39ae064bad677ed6717d98f5b83aca161189be7261d8efaf760"`
Dec 01 16:50:18.839 INFO running `"docker" "rm" "-f" "d371e7a6d7d4e39ae064bad677ed6717d98f5b83aca161189be7261d8efaf760"`
Dec 01 16:50:18.955 INFO [stdout] d371e7a6d7d4e39ae064bad677ed6717d98f5b83aca161189be7261d8efaf760
