Nov 28 13:20:24.408 INFO documenting hdf5-0.4.1 against try#f5a0bd723553ea4b7556bd7087b9f0919cafb483 for pr-55318 Nov 28 13:20:24.408 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55318/worker-1/try#f5a0bd723553ea4b7556bd7087b9f0919cafb483:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-55318/try#f5a0bd723553ea4b7556bd7087b9f0919cafb483:/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 +f5a0bd723553ea4b7556bd7087b9f0919cafb483-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 13:20:24.587 INFO [stdout] fc853f6f4be8a4fbd2c301c11785ee7ce401e02af8a02c1fbeba154b54544292 Nov 28 13:20:24.589 INFO running `"docker" "start" "-a" "fc853f6f4be8a4fbd2c301c11785ee7ce401e02af8a02c1fbeba154b54544292"` Nov 28 13:20:25.104 INFO [stderr] usermod: no changes Nov 28 13:20:25.138 INFO [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently Nov 28 13:20:25.138 INFO [stderr] disables Cargo from automatically inferring other test targets. Nov 28 13:20:25.138 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 28 13:20:25.138 INFO [stderr] files will be included as a test target: Nov 28 13:20:25.138 INFO [stderr] Nov 28 13:20:25.138 INFO [stderr] * /source/tests/write.rs Nov 28 13:20:25.138 INFO [stderr] * /source/tests/encode.rs Nov 28 13:20:25.138 INFO [stderr] Nov 28 13:20:25.138 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 28 13:20:25.138 INFO [stderr] ready to be compiled as a test target today. You can future-proof yourself Nov 28 13:20:25.138 INFO [stderr] and disable this warning by adding `autotests = false` to your [package] Nov 28 13:20:25.138 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 28 13:20:25.138 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 28 13:20:25.138 INFO [stderr] Nov 28 13:20:25.139 INFO [stderr] For more information on this warning you can consult Nov 28 13:20:25.139 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 28 13:20:25.146 INFO [stderr] Compiling hdf5-sys v0.4.1 Nov 28 13:20:26.355 INFO [stderr] Documenting hdf5 v0.4.1 (/source) Nov 28 13:20:27.986 INFO [stderr] warning: `[1]` cannot be resolved, ignoring it... Nov 28 13:20:27.986 INFO [stderr] --> src/lib.rs:1:25 Nov 28 13:20:27.986 INFO [stderr] | Nov 28 13:20:27.986 INFO [stderr] 1 | //! Interface to [HDF5][1]. Nov 28 13:20:27.986 INFO [stderr] | ^ cannot be resolved, ignoring Nov 28 13:20:27.986 INFO [stderr] | Nov 28 13:20:27.986 INFO [stderr] = note: #[warn(intra_doc_link_resolution_failure)] on by default Nov 28 13:20:27.986 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 13:20:27.986 INFO [stderr] Nov 28 13:20:27.987 INFO [stderr] warning: `[1]` cannot be resolved, ignoring it... Nov 28 13:20:27.987 INFO [stderr] --> src/lib.rs:1:25 Nov 28 13:20:27.987 INFO [stderr] | Nov 28 13:20:27.987 INFO [stderr] 1 | //! Interface to [HDF5][1]. Nov 28 13:20:27.987 INFO [stderr] | ^ cannot be resolved, ignoring Nov 28 13:20:27.987 INFO [stderr] | Nov 28 13:20:27.987 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 13:20:27.987 INFO [stderr] Nov 28 13:20:27.987 INFO [stderr] warning: `[2]` cannot be resolved, ignoring it... Nov 28 13:20:27.987 INFO [stderr] --> src/lib.rs:23:62 Nov 28 13:20:27.987 INFO [stderr] | Nov 28 13:20:27.987 INFO [stderr] 23 | //! Structural data can be written using [`rustc-serialize`][2] as follows: Nov 28 13:20:27.987 INFO [stderr] | ^ cannot be resolved, ignoring Nov 28 13:20:27.987 INFO [stderr] | Nov 28 13:20:27.987 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 13:20:27.987 INFO [stderr] Nov 28 13:20:28.098 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 2.96s Nov 28 13:20:28.098 INFO [stderr] su: No module specific data is present Nov 28 13:20:28.475 INFO running `"docker" "inspect" "fc853f6f4be8a4fbd2c301c11785ee7ce401e02af8a02c1fbeba154b54544292"` Nov 28 13:20:28.561 INFO running `"docker" "rm" "-f" "fc853f6f4be8a4fbd2c301c11785ee7ce401e02af8a02c1fbeba154b54544292"` Nov 28 13:20:28.715 INFO [stdout] fc853f6f4be8a4fbd2c301c11785ee7ce401e02af8a02c1fbeba154b54544292