Dec 02 01:49:18.128 INFO documenting tokio-core-0.1.17 against try#f86f76f89ea2b1ccbfb3741962ec2029d878a389 for pr-55318-1
Dec 02 01:49:18.129 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55318-1/worker-7/try#f86f76f89ea2b1ccbfb3741962ec2029d878a389:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/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 01:49:18.378 INFO [stdout] 662d0c62135b503f79cea27735d7f67b8a0153431b22b3e4005d8cf19fae2b47
Dec 02 01:49:18.380 INFO running `"docker" "start" "-a" "662d0c62135b503f79cea27735d7f67b8a0153431b22b3e4005d8cf19fae2b47"`
Dec 02 01:49:18.784 INFO [stderr] usermod: no changes
Dec 02 01:49:19.008 INFO [stderr]  Documenting tokio-core v0.1.17 (/source)
Dec 02 01:49:22.980 INFO [stderr] error: `[poll_read_ready]` cannot be resolved, ignoring it...
Dec 02 01:49:22.980 INFO [stderr]   --> src/reactor/poll_evented2.rs:40:6
Dec 02 01:49:22.980 INFO [stderr]    |
Dec 02 01:49:22.980 INFO [stderr] 40 | /// [`poll_read_ready`] and [`poll_write_ready`]. These functions return the
Dec 02 01:49:22.980 INFO [stderr]    |      ^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring
Dec 02 01:49:22.980 INFO [stderr]    |
Dec 02 01:49:22.980 INFO [stderr] note: lint level defined here
Dec 02 01:49:22.980 INFO [stderr]   --> src/lib.rs:94:9
Dec 02 01:49:22.980 INFO [stderr]    |
Dec 02 01:49:22.980 INFO [stderr] 94 | #![deny(warnings)]
Dec 02 01:49:22.980 INFO [stderr]    |         ^^^^^^^^
Dec 02 01:49:22.980 INFO [stderr]    = note: #[deny(intra_doc_link_resolution_failure)] implied by #[deny(warnings)]
Dec 02 01:49:22.980 INFO [stderr]    = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
Dec 02 01:49:22.980 INFO [stderr] 
Dec 02 01:49:22.980 INFO [stderr] error: `[poll_write_ready]` cannot be resolved, ignoring it...
Dec 02 01:49:22.980 INFO [stderr]   --> src/reactor/poll_evented2.rs:40:30
Dec 02 01:49:22.980 INFO [stderr]    |
Dec 02 01:49:22.980 INFO [stderr] 40 | /// [`poll_read_ready`] and [`poll_write_ready`]. These functions return the
Dec 02 01:49:22.980 INFO [stderr]    |                              ^^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring
Dec 02 01:49:22.980 INFO [stderr]    |
Dec 02 01:49:22.980 INFO [stderr]    = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
Dec 02 01:49:22.980 INFO [stderr] 
Dec 02 01:49:22.980 INFO [stderr] error: `[poll_read_ready]` cannot be resolved, ignoring it...
Dec 02 01:49:22.980 INFO [stderr]   --> src/reactor/poll_evented2.rs:42:6
Dec 02 01:49:22.980 INFO [stderr]    |
Dec 02 01:49:22.980 INFO [stderr] 42 | /// [`poll_read_ready`] indicates read readiness, immediately calling
Dec 02 01:49:22.980 INFO [stderr]    |      ^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring
Dec 02 01:49:22.980 INFO [stderr]    |
Dec 02 01:49:22.980 INFO [stderr]    = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
Dec 02 01:49:22.980 INFO [stderr] 
Dec 02 01:49:22.980 INFO [stderr] error: `[poll_read_ready]` cannot be resolved, ignoring it...
Dec 02 01:49:22.980 INFO [stderr]   --> src/reactor/poll_evented2.rs:43:6
Dec 02 01:49:22.980 INFO [stderr]    |
Dec 02 01:49:22.981 INFO [stderr] 43 | /// [`poll_read_ready`] again will also indicate read readiness.
Dec 02 01:49:22.981 INFO [stderr]    |      ^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring
Dec 02 01:49:22.981 INFO [stderr]    |
Dec 02 01:49:22.981 INFO [stderr]    = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
Dec 02 01:49:22.981 INFO [stderr] 
Dec 02 01:49:22.981 INFO [stderr] error: `[clear_read_ready]` cannot be resolved, ignoring it...
Dec 02 01:49:22.981 INFO [stderr]   --> src/reactor/poll_evented2.rs:46:53
Dec 02 01:49:22.981 INFO [stderr]    |
Dec 02 01:49:22.981 INFO [stderr] 46 | /// resource not being ready, the caller must call [`clear_read_ready`] or
Dec 02 01:49:22.981 INFO [stderr]    |                                                     ^^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring
Dec 02 01:49:22.981 INFO [stderr]    |
Dec 02 01:49:22.981 INFO [stderr]    = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
Dec 02 01:49:22.981 INFO [stderr] 
Dec 02 01:49:22.981 INFO [stderr] error: `[clear_write_ready]` cannot be resolved, ignoring it...
Dec 02 01:49:22.981 INFO [stderr]   --> src/reactor/poll_evented2.rs:47:6
Dec 02 01:49:22.981 INFO [stderr]    |
Dec 02 01:49:22.981 INFO [stderr] 47 | /// [`clear_write_ready`]. This clears the readiness state until a new readiness
Dec 02 01:49:22.981 INFO [stderr]    |      ^^^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring
Dec 02 01:49:22.981 INFO [stderr]    |
Dec 02 01:49:22.981 INFO [stderr]    = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
Dec 02 01:49:22.981 INFO [stderr] 
Dec 02 01:49:22.981 INFO [stderr] error: `[poll_read_ready]` cannot be resolved, ignoring it...
Dec 02 01:49:22.981 INFO [stderr]   --> src/reactor/poll_evented2.rs:51:54
Dec 02 01:49:22.981 INFO [stderr]    |
Dec 02 01:49:22.981 INFO [stderr] 51 | /// [`TcpListener`] implements poll_accept by using [`poll_read_ready`] and
Dec 02 01:49:22.981 INFO [stderr]    |                                                      ^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring
Dec 02 01:49:22.981 INFO [stderr]    |
Dec 02 01:49:22.981 INFO [stderr]    = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
Dec 02 01:49:22.981 INFO [stderr] 
Dec 02 01:49:22.981 INFO [stderr] error: `[clear_write_ready]` cannot be resolved, ignoring it...
Dec 02 01:49:22.981 INFO [stderr]   --> src/reactor/poll_evented2.rs:52:6
Dec 02 01:49:22.981 INFO [stderr]    |
Dec 02 01:49:22.981 INFO [stderr] 52 | /// [`clear_write_ready`].
Dec 02 01:49:22.981 INFO [stderr]    |      ^^^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring
Dec 02 01:49:22.981 INFO [stderr]    |
Dec 02 01:49:22.981 INFO [stderr]    = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
Dec 02 01:49:22.981 INFO [stderr] 
Dec 02 01:49:23.074 INFO [stderr] error: Could not document `tokio-core`.
Dec 02 01:49:23.074 INFO [stderr] 
Dec 02 01:49:23.074 INFO [stderr] Caused by:
Dec 02 01:49:23.074 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-8b7791e26a4b5331.rmeta --extern futures=/target/debug/deps/libfutures-15083c395d8053ea.rmeta --extern iovec=/target/debug/deps/libiovec-c1c9f85b01535779.rmeta --extern log=/target/debug/deps/liblog-916819fb5d5f3ba7.rmeta --extern mio=/target/debug/deps/libmio-d632ed77168f372b.rmeta --extern scoped_tls=/target/debug/deps/libscoped_tls-7d0f7c90f35af009.rmeta --extern tokio=/target/debug/deps/libtokio-d1a582097b194292.rmeta --extern tokio_executor=/target/debug/deps/libtokio_executor-3a1ff46776fd3228.rmeta --extern tokio_io=/target/debug/deps/libtokio_io-c1718597844b7492.rmeta --extern tokio_reactor=/target/debug/deps/libtokio_reactor-2c46f364ff647f77.rmeta --extern tokio_timer=/target/debug/deps/libtokio_timer-fbb434356364e32c.rmeta --cap-lints=forbid` (exit code: 1)
Dec 02 01:49:23.074 INFO [stderr] su: No module specific data is present
Dec 02 01:49:23.394 INFO running `"docker" "inspect" "662d0c62135b503f79cea27735d7f67b8a0153431b22b3e4005d8cf19fae2b47"`
Dec 02 01:49:23.508 INFO running `"docker" "rm" "-f" "662d0c62135b503f79cea27735d7f67b8a0153431b22b3e4005d8cf19fae2b47"`
Dec 02 01:49:23.604 INFO [stdout] 662d0c62135b503f79cea27735d7f67b8a0153431b22b3e4005d8cf19fae2b47