Dec 02 07:37:39.157 INFO documenting git-clean-0.5.1 against try#f86f76f89ea2b1ccbfb3741962ec2029d878a389 for pr-55318-1 Dec 02 07:37:39.158 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55318-1/worker-4/try#f86f76f89ea2b1ccbfb3741962ec2029d878a389:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/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 02 07:37:39.686 INFO [stdout] b20e32cc8cb848599842f6686c775042f6a63b603a34c5918e4073f3f5692340 Dec 02 07:37:39.688 INFO running `"docker" "start" "-a" "b20e32cc8cb848599842f6686c775042f6a63b603a34c5918e4073f3f5692340"` Dec 02 07:37:41.069 INFO [stderr] usermod: no changes Dec 02 07:37:41.152 INFO [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently Dec 02 07:37:41.152 INFO [stderr] disables Cargo from automatically inferring other test targets. Dec 02 07:37:41.152 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 02 07:37:41.152 INFO [stderr] files will be included as a test target: Dec 02 07:37:41.152 INFO [stderr] Dec 02 07:37:41.152 INFO [stderr] * /source/tests/remote.rs Dec 02 07:37:41.152 INFO [stderr] * /source/tests/utility.rs Dec 02 07:37:41.152 INFO [stderr] * /source/tests/local.rs Dec 02 07:37:41.152 INFO [stderr] * /source/tests/support.rs Dec 02 07:37:41.152 INFO [stderr] * /source/tests/deletion.rs Dec 02 07:37:41.152 INFO [stderr] Dec 02 07:37:41.152 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 02 07:37:41.152 INFO [stderr] ready to be compiled as a test target today. You can future-proof yourself Dec 02 07:37:41.152 INFO [stderr] and disable this warning by adding `autotests = false` to your [package] Dec 02 07:37:41.152 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 02 07:37:41.152 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 02 07:37:41.152 INFO [stderr] Dec 02 07:37:41.152 INFO [stderr] For more information on this warning you can consult Dec 02 07:37:41.152 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 02 07:37:41.164 INFO [stderr] Documenting git-clean v0.5.1 (/source) Dec 02 07:37:42.907 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 1.79s Dec 02 07:37:42.907 INFO [stderr] su: No module specific data is present Dec 02 07:37:43.258 INFO running `"docker" "inspect" "b20e32cc8cb848599842f6686c775042f6a63b603a34c5918e4073f3f5692340"` Dec 02 07:37:43.382 INFO running `"docker" "rm" "-f" "b20e32cc8cb848599842f6686c775042f6a63b603a34c5918e4073f3f5692340"` Dec 02 07:37:43.483 INFO [stdout] b20e32cc8cb848599842f6686c775042f6a63b603a34c5918e4073f3f5692340