Dec 02 06:55:29.277 INFO documenting hdf5-0.4.1 against master#147e60c5f89cfa2d3ffc247413956a37582c98e7 for pr-55318-1
Dec 02 06:55:29.277 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 02 06:55:29.778 INFO [stdout] 73631e25a9a59be1225e7f783d32733f6512ed26da3db892fe518021f5ecfcbb
Dec 02 06:55:29.779 INFO running `"docker" "start" "-a" "73631e25a9a59be1225e7f783d32733f6512ed26da3db892fe518021f5ecfcbb"`
Dec 02 06:55:30.176 INFO [stderr] usermod: no changes
Dec 02 06:55:30.215 INFO [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently
Dec 02 06:55:30.215 INFO [stderr] disables Cargo from automatically inferring other test targets.
Dec 02 06:55:30.215 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 02 06:55:30.215 INFO [stderr] files will be included as a test target:
Dec 02 06:55:30.215 INFO [stderr] 
Dec 02 06:55:30.215 INFO [stderr] * /source/tests/write.rs
Dec 02 06:55:30.215 INFO [stderr] * /source/tests/encode.rs
Dec 02 06:55:30.215 INFO [stderr] 
Dec 02 06:55:30.215 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 02 06:55:30.215 INFO [stderr] ready to be compiled as a test target today. You can future-proof yourself
Dec 02 06:55:30.215 INFO [stderr] and disable this warning by adding `autotests = false` to your [package]
Dec 02 06:55:30.215 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 02 06:55:30.215 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 02 06:55:30.215 INFO [stderr] 
Dec 02 06:55:30.215 INFO [stderr] For more information on this warning you can consult
Dec 02 06:55:30.215 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 02 06:55:30.222 INFO [stderr]    Compiling hdf5-sys v0.4.1
Dec 02 06:55:31.400 INFO [stderr]  Documenting hdf5 v0.4.1 (/source)
Dec 02 06:55:33.074 INFO [stderr] warning: `[1]` cannot be resolved, ignoring it...
Dec 02 06:55:33.074 INFO [stderr]  --> src/lib.rs:1:25
Dec 02 06:55:33.074 INFO [stderr]   |
Dec 02 06:55:33.074 INFO [stderr] 1 | //! Interface to [HDF5][1].
Dec 02 06:55:33.074 INFO [stderr]   |                         ^ cannot be resolved, ignoring
Dec 02 06:55:33.074 INFO [stderr]   |
Dec 02 06:55:33.074 INFO [stderr]   = note: #[warn(intra_doc_link_resolution_failure)] on by default
Dec 02 06:55:33.074 INFO [stderr]   = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
Dec 02 06:55:33.074 INFO [stderr] 
Dec 02 06:55:33.074 INFO [stderr] warning: `[1]` cannot be resolved, ignoring it...
Dec 02 06:55:33.074 INFO [stderr]  --> src/lib.rs:1:25
Dec 02 06:55:33.074 INFO [stderr]   |
Dec 02 06:55:33.074 INFO [stderr] 1 | //! Interface to [HDF5][1].
Dec 02 06:55:33.074 INFO [stderr]   |                         ^ cannot be resolved, ignoring
Dec 02 06:55:33.074 INFO [stderr]   |
Dec 02 06:55:33.080 INFO [stderr]   = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
Dec 02 06:55:33.080 INFO [stderr] 
Dec 02 06:55:33.080 INFO [stderr] warning: `[2]` cannot be resolved, ignoring it...
Dec 02 06:55:33.080 INFO [stderr]   --> src/lib.rs:23:62
Dec 02 06:55:33.080 INFO [stderr]    |
Dec 02 06:55:33.080 INFO [stderr] 23 | //! Structural data can be written using [`rustc-serialize`][2] as follows:
Dec 02 06:55:33.080 INFO [stderr]    |                                                              ^ cannot be resolved, ignoring
Dec 02 06:55:33.080 INFO [stderr]    |
Dec 02 06:55:33.080 INFO [stderr]    = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
Dec 02 06:55:33.080 INFO [stderr] 
Dec 02 06:55:33.186 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.98s
Dec 02 06:55:33.190 INFO [stderr] su: No module specific data is present
Dec 02 06:55:33.586 INFO running `"docker" "inspect" "73631e25a9a59be1225e7f783d32733f6512ed26da3db892fe518021f5ecfcbb"`
Dec 02 06:55:33.674 INFO running `"docker" "rm" "-f" "73631e25a9a59be1225e7f783d32733f6512ed26da3db892fe518021f5ecfcbb"`
Dec 02 06:55:33.834 INFO [stdout] 73631e25a9a59be1225e7f783d32733f6512ed26da3db892fe518021f5ecfcbb