Nov 28 03:54:41.625 INFO documenting PhilippRichter/rust-blockparser against master#6bfb46e4ac9a2704f06de1a2ff7a4612cd70c8cb for pr-55318 Nov 28 03:54:41.627 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55318/worker-1/master#6bfb46e4ac9a2704f06de1a2ff7a4612cd70c8cb:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/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 03:54:42.146 INFO [stdout] 22f5e284a4817b2fd3ac6085690a0430883b7398158587f604a476e644f98b13 Nov 28 03:54:42.156 INFO running `"docker" "start" "-a" "22f5e284a4817b2fd3ac6085690a0430883b7398158587f604a476e644f98b13"` Nov 28 03:54:42.995 INFO [stderr] usermod: no changes Nov 28 03:54:43.091 INFO [stderr] Checking bech32 v0.5.0 Nov 28 03:54:43.091 INFO [stderr] Compiling secp256k1 v0.11.1 Nov 28 03:54:43.956 INFO [stderr] Checking bitcoin-bech32 v0.8.0 Nov 28 03:54:45.825 INFO [stderr] Checking bitcoin v0.14.1 Nov 28 03:54:49.340 INFO [stderr] Documenting rust-blockparser v0.1.0 (/source) Nov 28 03:54:51.695 INFO [stderr] warning: `[u8]` cannot be resolved, ignoring it... Nov 28 03:54:51.696 INFO [stderr] --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/rust-crypto-0.2.36/src/mac.rs:36:5 Nov 28 03:54:51.696 INFO [stderr] | Nov 28 03:54:51.696 INFO [stderr] 36 | / /** Nov 28 03:54:51.697 INFO [stderr] 37 | | * Obtain the result of a Mac computation as [u8]. This method should be used very carefully Nov 28 03:54:51.697 INFO [stderr] 38 | | * since incorrect use of the Mac code could result in permitting a timing attack which defeats Nov 28 03:54:51.697 INFO [stderr] 39 | | * the security provided by a Mac function. Nov 28 03:54:51.697 INFO [stderr] 40 | | */ Nov 28 03:54:51.697 INFO [stderr] | |_______^ Nov 28 03:54:51.698 INFO [stderr] | Nov 28 03:54:51.698 INFO [stderr] = note: #[warn(intra_doc_link_resolution_failure)] on by default Nov 28 03:54:51.698 INFO [stderr] = note: the link appears in this line: Nov 28 03:54:51.699 INFO [stderr] Nov 28 03:54:51.699 INFO [stderr] Obtain the result of a Mac computation as [u8]. This method should be used very carefully Nov 28 03:54:51.699 INFO [stderr] ^^ Nov 28 03:54:51.699 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 03:54:51.700 INFO [stderr] Nov 28 03:54:51.804 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 8.78s Nov 28 03:54:51.819 INFO [stderr] su: No module specific data is present Nov 28 03:54:52.391 INFO running `"docker" "inspect" "22f5e284a4817b2fd3ac6085690a0430883b7398158587f604a476e644f98b13"` Nov 28 03:54:52.815 INFO running `"docker" "rm" "-f" "22f5e284a4817b2fd3ac6085690a0430883b7398158587f604a476e644f98b13"` Nov 28 03:54:53.263 INFO [stdout] 22f5e284a4817b2fd3ac6085690a0430883b7398158587f604a476e644f98b13