Sep 01 09:11:59.039 INFO checking burst-pool-0.5.1 against try#a5b9f2cc0cdaca8edf23a89c649279de2c91cd3b for pr-53578 Sep 01 09:11:59.040 INFO running: cargo +a5b9f2cc0cdaca8edf23a89c649279de2c91cd3b-alt check --frozen --all --all-targets Sep 01 09:11:59.040 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-1/pr-53578/try#a5b9f2cc0cdaca8edf23a89c649279de2c91cd3b:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53578/worker-1/try#a5b9f2cc0cdaca8edf23a89c649279de2c91cd3b:/target:rw,Z" "-v" "/home/ec2-user/crater/./work/local/cargo-home:/cargo-home:ro,Z" "-v" "/home/ec2-user/crater/./work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=500" "-e" "CMD=cargo +a5b9f2cc0cdaca8edf23a89c649279de2c91cd3b-alt check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-m" "2G" "crater"` Sep 01 09:11:59.206 INFO blam! d8e55b68a0cf88fa28f6dcb3eaf7a7776714dfe3ff1333cabaf0f7c9eaef2769 Sep 01 09:11:59.208 INFO running `"docker" "start" "-a" "d8e55b68a0cf88fa28f6dcb3eaf7a7776714dfe3ff1333cabaf0f7c9eaef2769"` Sep 01 09:11:59.903 INFO kablam! warning: An explicit [[bench]] section is specified in Cargo.toml which currently Sep 01 09:11:59.903 INFO kablam! disables Cargo from automatically inferring other benchmark targets. Sep 01 09:11:59.903 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following Sep 01 09:11:59.903 INFO kablam! files will be included as a benchmark target: Sep 01 09:11:59.903 INFO kablam! Sep 01 09:11:59.903 INFO kablam! * /source/benches/settings.rs Sep 01 09:11:59.903 INFO kablam! * /source/benches/stats.rs Sep 01 09:11:59.903 INFO kablam! Sep 01 09:11:59.903 INFO kablam! This is likely to break cargo build or cargo test as these files may not be Sep 01 09:11:59.903 INFO kablam! ready to be compiled as a benchmark target today. You can future-proof yourself Sep 01 09:11:59.904 INFO kablam! and disable this warning by adding `autobenches = false` to your [package] Sep 01 09:11:59.904 INFO kablam! section. You may also move the files to a location where Cargo would not Sep 01 09:11:59.904 INFO kablam! automatically infer them to be a target, such as in subfolders. Sep 01 09:11:59.904 INFO kablam! Sep 01 09:11:59.904 INFO kablam! For more information on this warning you can consult Sep 01 09:11:59.904 INFO kablam! https://github.com/rust-lang/cargo/issues/5330 Sep 01 09:11:59.935 INFO kablam! Checking spmc v0.2.2 Sep 01 09:11:59.935 INFO kablam! Checking nix v0.9.0 Sep 01 09:12:00.113 INFO kablam! error: expected one of `!`, `(`, `)`, `,`, `::`, or `<`, found `.` Sep 01 09:12:00.113 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/nix-0.9.0/src/sys/socket/mod.rs:637:36 Sep 01 09:12:00.113 INFO kablam! | Sep 01 09:12:00.113 INFO kablam! 637 | if len < mem::size_of_val(&addr.ss_family) { Sep 01 09:12:00.113 INFO kablam! | ^ expected one of `!`, `(`, `)`, `,`, `::`, or `<` here Sep 01 09:12:00.113 INFO kablam! Sep 01 09:12:05.693 INFO kablam! error: aborting due to previous error Sep 01 09:12:05.693 INFO kablam! Sep 01 09:12:05.705 INFO kablam! error: Could not compile `nix`. Sep 01 09:12:05.705 INFO kablam! Sep 01 09:12:05.705 INFO kablam! To learn more, run the command again with --verbose. Sep 01 09:12:05.707 INFO kablam! su: No module specific data is present Sep 01 09:12:06.316 INFO running `"docker" "rm" "-f" "d8e55b68a0cf88fa28f6dcb3eaf7a7776714dfe3ff1333cabaf0f7c9eaef2769"` Sep 01 09:12:06.441 INFO blam! d8e55b68a0cf88fa28f6dcb3eaf7a7776714dfe3ff1333cabaf0f7c9eaef2769