Nov 28 08:08:27.917 INFO documenting tokio-core-0.1.17 against try#f5a0bd723553ea4b7556bd7087b9f0919cafb483 for pr-55318 Nov 28 08:08:27.917 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55318/worker-6/try#f5a0bd723553ea4b7556bd7087b9f0919cafb483:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-6/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 08:08:28.153 INFO [stdout] 71b08019cf9c2d77fb7a808f980e367dc30311b29f4c1fad2fd24ba39ac32c5c Nov 28 08:08:28.155 INFO running `"docker" "start" "-a" "71b08019cf9c2d77fb7a808f980e367dc30311b29f4c1fad2fd24ba39ac32c5c"` Nov 28 08:08:28.633 INFO [stderr] usermod: no changes Nov 28 08:08:28.799 INFO [stderr] Documenting tokio-core v0.1.17 (/source) Nov 28 08:08:32.626 INFO [stderr] error: `[poll_read_ready]` cannot be resolved, ignoring it... Nov 28 08:08:32.626 INFO [stderr] --> src/reactor/poll_evented2.rs:40:6 Nov 28 08:08:32.626 INFO [stderr] | Nov 28 08:08:32.626 INFO [stderr] 40 | /// [`poll_read_ready`] and [`poll_write_ready`]. These functions return the Nov 28 08:08:32.627 INFO [stderr] | ^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Nov 28 08:08:32.627 INFO [stderr] | Nov 28 08:08:32.627 INFO [stderr] note: lint level defined here Nov 28 08:08:32.627 INFO [stderr] --> src/lib.rs:94:9 Nov 28 08:08:32.627 INFO [stderr] | Nov 28 08:08:32.627 INFO [stderr] 94 | #![deny(warnings)] Nov 28 08:08:32.628 INFO [stderr] | ^^^^^^^^ Nov 28 08:08:32.628 INFO [stderr] = note: #[deny(intra_doc_link_resolution_failure)] implied by #[deny(warnings)] Nov 28 08:08:32.628 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 08:08:32.628 INFO [stderr] Nov 28 08:08:32.628 INFO [stderr] error: `[poll_write_ready]` cannot be resolved, ignoring it... Nov 28 08:08:32.628 INFO [stderr] --> src/reactor/poll_evented2.rs:40:30 Nov 28 08:08:32.628 INFO [stderr] | Nov 28 08:08:32.628 INFO [stderr] 40 | /// [`poll_read_ready`] and [`poll_write_ready`]. These functions return the Nov 28 08:08:32.628 INFO [stderr] | ^^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Nov 28 08:08:32.628 INFO [stderr] | Nov 28 08:08:32.628 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 08:08:32.628 INFO [stderr] Nov 28 08:08:32.628 INFO [stderr] error: `[poll_read_ready]` cannot be resolved, ignoring it... Nov 28 08:08:32.628 INFO [stderr] --> src/reactor/poll_evented2.rs:42:6 Nov 28 08:08:32.628 INFO [stderr] | Nov 28 08:08:32.628 INFO [stderr] 42 | /// [`poll_read_ready`] indicates read readiness, immediately calling Nov 28 08:08:32.628 INFO [stderr] | ^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Nov 28 08:08:32.628 INFO [stderr] | Nov 28 08:08:32.628 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 08:08:32.628 INFO [stderr] Nov 28 08:08:32.628 INFO [stderr] error: `[poll_read_ready]` cannot be resolved, ignoring it... Nov 28 08:08:32.628 INFO [stderr] --> src/reactor/poll_evented2.rs:43:6 Nov 28 08:08:32.628 INFO [stderr] | Nov 28 08:08:32.628 INFO [stderr] 43 | /// [`poll_read_ready`] again will also indicate read readiness. Nov 28 08:08:32.628 INFO [stderr] | ^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Nov 28 08:08:32.628 INFO [stderr] | Nov 28 08:08:32.628 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 08:08:32.628 INFO [stderr] Nov 28 08:08:32.628 INFO [stderr] error: `[clear_read_ready]` cannot be resolved, ignoring it... Nov 28 08:08:32.628 INFO [stderr] --> src/reactor/poll_evented2.rs:46:53 Nov 28 08:08:32.628 INFO [stderr] | Nov 28 08:08:32.628 INFO [stderr] 46 | /// resource not being ready, the caller must call [`clear_read_ready`] or Nov 28 08:08:32.628 INFO [stderr] | ^^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Nov 28 08:08:32.628 INFO [stderr] | Nov 28 08:08:32.628 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 08:08:32.628 INFO [stderr] Nov 28 08:08:32.628 INFO [stderr] error: `[clear_write_ready]` cannot be resolved, ignoring it... Nov 28 08:08:32.628 INFO [stderr] --> src/reactor/poll_evented2.rs:47:6 Nov 28 08:08:32.628 INFO [stderr] | Nov 28 08:08:32.628 INFO [stderr] 47 | /// [`clear_write_ready`]. This clears the readiness state until a new readiness Nov 28 08:08:32.628 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Nov 28 08:08:32.628 INFO [stderr] | Nov 28 08:08:32.628 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 08:08:32.628 INFO [stderr] Nov 28 08:08:32.628 INFO [stderr] error: `[poll_read_ready]` cannot be resolved, ignoring it... Nov 28 08:08:32.628 INFO [stderr] --> src/reactor/poll_evented2.rs:51:54 Nov 28 08:08:32.628 INFO [stderr] | Nov 28 08:08:32.628 INFO [stderr] 51 | /// [`TcpListener`] implements poll_accept by using [`poll_read_ready`] and Nov 28 08:08:32.628 INFO [stderr] | ^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Nov 28 08:08:32.628 INFO [stderr] | Nov 28 08:08:32.628 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 08:08:32.628 INFO [stderr] Nov 28 08:08:32.628 INFO [stderr] error: `[clear_write_ready]` cannot be resolved, ignoring it... Nov 28 08:08:32.628 INFO [stderr] --> src/reactor/poll_evented2.rs:52:6 Nov 28 08:08:32.628 INFO [stderr] | Nov 28 08:08:32.628 INFO [stderr] 52 | /// [`clear_write_ready`]. Nov 28 08:08:32.628 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Nov 28 08:08:32.628 INFO [stderr] | Nov 28 08:08:32.628 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 08:08:32.628 INFO [stderr] Nov 28 08:08:32.715 INFO [stderr] error: Could not document `tokio-core`. Nov 28 08:08:32.715 INFO [stderr] Nov 28 08:08:32.715 INFO [stderr] Caused by: Nov 28 08:08:32.715 INFO [stderr] process didn't exit successfully: `rustdoc --crate-name tokio_core src/lib.rs --color never -o /target/doc --document-private-items -L dependency=/target/debug/deps --extern bytes=/target/debug/deps/libbytes-b736d178dbb5c9ed.rmeta --extern futures=/target/debug/deps/libfutures-b008a101f8780b8c.rmeta --extern iovec=/target/debug/deps/libiovec-f69d2b77d5cb212b.rmeta --extern log=/target/debug/deps/liblog-7108ccf313b638d2.rmeta --extern mio=/target/debug/deps/libmio-0b8f2e5b778ffa5a.rmeta --extern scoped_tls=/target/debug/deps/libscoped_tls-89051aa89087bfee.rmeta --extern tokio=/target/debug/deps/libtokio-cfee6e48451d70aa.rmeta --extern tokio_executor=/target/debug/deps/libtokio_executor-a6999da63f7f2a5c.rmeta --extern tokio_io=/target/debug/deps/libtokio_io-d3d50b878cd9222f.rmeta --extern tokio_reactor=/target/debug/deps/libtokio_reactor-579eb28186a8f0ab.rmeta --extern tokio_timer=/target/debug/deps/libtokio_timer-ebbb9a507827858d.rmeta --cap-lints=forbid` (exit code: 1) Nov 28 08:08:32.715 INFO [stderr] su: No module specific data is present Nov 28 08:08:32.944 INFO running `"docker" "inspect" "71b08019cf9c2d77fb7a808f980e367dc30311b29f4c1fad2fd24ba39ac32c5c"` Nov 28 08:08:33.056 INFO running `"docker" "rm" "-f" "71b08019cf9c2d77fb7a808f980e367dc30311b29f4c1fad2fd24ba39ac32c5c"` Nov 28 08:08:33.164 INFO [stdout] 71b08019cf9c2d77fb7a808f980e367dc30311b29f4c1fad2fd24ba39ac32c5c