Dec 01 18:40:10.429 INFO documenting bpglaser/red-mountain-resize against master#147e60c5f89cfa2d3ffc247413956a37582c98e7 for pr-55318-1
Dec 01 18:40:10.430 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55318-1/worker-3/master#147e60c5f89cfa2d3ffc247413956a37582c98e7:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/pr-55318-1/master#147e60c5f89cfa2d3ffc247413956a37582c98e7:/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 +147e60c5f89cfa2d3ffc247413956a37582c98e7-alt doc --frozen --no-deps --document-private-items" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 01 18:40:10.784 INFO [stdout] fd3ee6b99f8177110ba7ce7c7b1b77b185af55d2187b80dbce40eb893cf49938
Dec 01 18:40:10.788 INFO running `"docker" "start" "-a" "fd3ee6b99f8177110ba7ce7c7b1b77b185af55d2187b80dbce40eb893cf49938"`
Dec 01 18:40:11.870 INFO [stderr] usermod: no changes
Dec 01 18:40:11.976 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 01 18:40:11.976 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 01 18:40:11.976 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 01 18:40:11.976 INFO [stderr] files will be included as a binary target:
Dec 01 18:40:11.976 INFO [stderr] 
Dec 01 18:40:11.976 INFO [stderr] * /source/src/bin/main.rs
Dec 01 18:40:11.976 INFO [stderr] 
Dec 01 18:40:11.976 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 01 18:40:11.976 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 01 18:40:11.976 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 01 18:40:11.976 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 01 18:40:11.976 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 01 18:40:11.976 INFO [stderr] 
Dec 01 18:40:11.976 INFO [stderr] For more information on this warning you can consult
Dec 01 18:40:11.976 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 01 18:40:11.976 INFO [stderr] warning: path `/source/src/bin/main.rs` was erroneously implicitly accepted for binary `rmr`,
Dec 01 18:40:11.976 INFO [stderr] please set bin.path in Cargo.toml
Dec 01 18:40:12.056 INFO [stderr]     Checking enum_primitive v0.1.1
Dec 01 18:40:12.056 INFO [stderr]     Checking rayon-core v1.2.1
Dec 01 18:40:12.056 INFO [stderr]     Checking num-rational v0.1.38
Dec 01 18:40:12.056 INFO [stderr]     Checking png v0.6.2
Dec 01 18:40:14.306 INFO [stderr]     Checking rayon v0.8.1
Dec 01 18:40:17.218 INFO [stderr]     Checking jpeg-decoder v0.1.13
Dec 01 18:40:18.666 INFO [stderr]     Checking image v0.12.4
Dec 01 18:40:22.898 INFO [stderr]  Documenting rmr v0.3.0 (/source)
Dec 01 18:40:26.096 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 14.18s
Dec 01 18:40:26.109 INFO [stderr] su: No module specific data is present
Dec 01 18:40:27.014 INFO running `"docker" "inspect" "fd3ee6b99f8177110ba7ce7c7b1b77b185af55d2187b80dbce40eb893cf49938"`
Dec 01 18:40:27.342 INFO running `"docker" "rm" "-f" "fd3ee6b99f8177110ba7ce7c7b1b77b185af55d2187b80dbce40eb893cf49938"`
Dec 01 18:40:27.656 INFO [stdout] fd3ee6b99f8177110ba7ce7c7b1b77b185af55d2187b80dbce40eb893cf49938