Dec 01 04:28:43.167 INFO documenting vexyz/vexyz_math against try#f86f76f89ea2b1ccbfb3741962ec2029d878a389 for pr-55318-1
Dec 01 04:28:43.168 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55318-1/worker-1/try#f86f76f89ea2b1ccbfb3741962ec2029d878a389:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-55318-1/try#f86f76f89ea2b1ccbfb3741962ec2029d878a389:/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 +f86f76f89ea2b1ccbfb3741962ec2029d878a389-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 04:28:43.734 INFO [stdout] 137528ffb51690ed582516477c329f71a5782cc4489f9b733c6529421872f03a
Dec 01 04:28:43.738 INFO running `"docker" "start" "-a" "137528ffb51690ed582516477c329f71a5782cc4489f9b733c6529421872f03a"`
Dec 01 04:28:44.896 INFO [stderr] usermod: no changes
Dec 01 04:28:44.932 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 01 04:28:44.932 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 01 04:28:44.932 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 01 04:28:44.932 INFO [stderr] files will be included as a binary target:
Dec 01 04:28:44.932 INFO [stderr] 
Dec 01 04:28:44.932 INFO [stderr] * /source/src/main.rs
Dec 01 04:28:44.932 INFO [stderr] 
Dec 01 04:28:44.932 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 01 04:28:44.932 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 01 04:28:44.932 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 01 04:28:44.932 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 01 04:28:44.932 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 01 04:28:44.932 INFO [stderr] 
Dec 01 04:28:44.932 INFO [stderr] For more information on this warning you can consult
Dec 01 04:28:44.932 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 01 04:28:44.932 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `vexyz_math_run`,
Dec 01 04:28:44.933 INFO [stderr] please set bin.path in Cargo.toml
Dec 01 04:28:44.933 INFO [stderr]     Checking vexyz_math v0.0.1 (/source)
Dec 01 04:28:44.933 INFO [stderr]  Documenting vexyz_math v0.0.1 (/source)
Dec 01 04:28:45.454 INFO [stderr] warning: unused import: `std::mem`
Dec 01 04:28:45.454 INFO [stderr]  --> src/vec2.rs:4:5
Dec 01 04:28:45.454 INFO [stderr]   |
Dec 01 04:28:45.454 INFO [stderr] 4 | use std::mem;
Dec 01 04:28:45.454 INFO [stderr]   |     ^^^^^^^^
Dec 01 04:28:45.454 INFO [stderr]   |
Dec 01 04:28:45.454 INFO [stderr]   = note: #[warn(unused_imports)] on by default
Dec 01 04:28:45.454 INFO [stderr] 
Dec 01 04:28:45.456 INFO [stderr] warning: unused import: `std::mem`
Dec 01 04:28:45.456 INFO [stderr]  --> src/vec3.rs:4:5
Dec 01 04:28:45.456 INFO [stderr]   |
Dec 01 04:28:45.456 INFO [stderr] 4 | use std::mem;
Dec 01 04:28:45.456 INFO [stderr]   |     ^^^^^^^^
Dec 01 04:28:45.456 INFO [stderr] 
Dec 01 04:28:45.456 INFO [stderr] warning: unused import: `std::mem`
Dec 01 04:28:45.456 INFO [stderr]  --> src/vec4.rs:4:5
Dec 01 04:28:45.456 INFO [stderr]   |
Dec 01 04:28:45.456 INFO [stderr] 4 | use std::mem;
Dec 01 04:28:45.456 INFO [stderr]   |     ^^^^^^^^
Dec 01 04:28:45.456 INFO [stderr] 
Dec 01 04:28:48.901 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 3.99s
Dec 01 04:28:48.903 INFO [stderr] su: No module specific data is present
Dec 01 04:28:50.188 INFO running `"docker" "inspect" "137528ffb51690ed582516477c329f71a5782cc4489f9b733c6529421872f03a"`
Dec 01 04:28:50.482 INFO running `"docker" "rm" "-f" "137528ffb51690ed582516477c329f71a5782cc4489f9b733c6529421872f03a"`
Dec 01 04:28:50.964 INFO [stdout] 137528ffb51690ed582516477c329f71a5782cc4489f9b733c6529421872f03a