Nov 28 02:38:50.547 INFO documenting Yatekii/rust_playground against master#6bfb46e4ac9a2704f06de1a2ff7a4612cd70c8cb for pr-55318
Nov 28 02:38:50.548 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55318/worker-3/master#6bfb46e4ac9a2704f06de1a2ff7a4612cd70c8cb:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/pr-55318/master#6bfb46e4ac9a2704f06de1a2ff7a4612cd70c8cb:/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 +6bfb46e4ac9a2704f06de1a2ff7a4612cd70c8cb-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"`
Nov 28 02:38:50.875 INFO [stdout] 73b7bcb4902a5382f625a567e4aaf8132d0ad652b128adc805f701a6f16528e7
Nov 28 02:38:50.879 INFO running `"docker" "start" "-a" "73b7bcb4902a5382f625a567e4aaf8132d0ad652b128adc805f701a6f16528e7"`
Nov 28 02:38:52.091 INFO [stderr] usermod: no changes
Nov 28 02:38:52.275 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Nov 28 02:38:52.275 INFO [stderr] disables Cargo from automatically inferring other benchmark targets.
Nov 28 02:38:52.275 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 28 02:38:52.275 INFO [stderr] files will be included as a benchmark target:
Nov 28 02:38:52.275 INFO [stderr] 
Nov 28 02:38:52.275 INFO [stderr] * /source/benches/cell.rs
Nov 28 02:38:52.275 INFO [stderr] 
Nov 28 02:38:52.275 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 28 02:38:52.275 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
Nov 28 02:38:52.275 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package]
Nov 28 02:38:52.275 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 28 02:38:52.275 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 28 02:38:52.275 INFO [stderr] 
Nov 28 02:38:52.275 INFO [stderr] For more information on this warning you can consult
Nov 28 02:38:52.275 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 28 02:38:52.403 INFO [stderr]     Checking elapsed v0.1.2
Nov 28 02:38:52.421 INFO [stderr]     Checking num-complex v0.2.0
Nov 28 02:38:52.421 INFO [stderr]     Checking approx v0.2.0
Nov 28 02:38:54.085 INFO [stderr]     Checking alga v0.6.0
Nov 28 02:38:57.856 INFO [stderr]     Checking nalgebra v0.15.3
Nov 28 02:39:28.017 INFO [stderr]     Checking ncollide2d v0.16.1
Nov 28 02:39:35.652 INFO [stderr]  Documenting rust_playground v0.1.0 (/source)
Nov 28 02:39:38.642 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 46.52s
Nov 28 02:39:38.657 INFO [stderr] su: No module specific data is present
Nov 28 02:39:39.331 INFO running `"docker" "inspect" "73b7bcb4902a5382f625a567e4aaf8132d0ad652b128adc805f701a6f16528e7"`
Nov 28 02:39:39.630 INFO running `"docker" "rm" "-f" "73b7bcb4902a5382f625a567e4aaf8132d0ad652b128adc805f701a6f16528e7"`
Nov 28 02:39:39.859 INFO [stdout] 73b7bcb4902a5382f625a567e4aaf8132d0ad652b128adc805f701a6f16528e7