Dec 02 01:49:18.194 INFO documenting tokio-core-0.1.17 against master#147e60c5f89cfa2d3ffc247413956a37582c98e7 for pr-55318-1 Dec 02 01:49:18.194 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55318-1/worker-5/master#147e60c5f89cfa2d3ffc247413956a37582c98e7:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/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 01:49:18.428 INFO [stdout] b8ff35692b2b3e431621af6548aa846e1eec3dad3485f103c79ff9bbaf71fa8d Dec 02 01:49:18.434 INFO running `"docker" "start" "-a" "b8ff35692b2b3e431621af6548aa846e1eec3dad3485f103c79ff9bbaf71fa8d"` Dec 02 01:49:18.892 INFO [stderr] usermod: no changes Dec 02 01:49:19.106 INFO [stderr] Documenting tokio-core v0.1.17 (/source) Dec 02 01:49:23.297 INFO [stderr] error: `[poll_read_ready]` cannot be resolved, ignoring it... Dec 02 01:49:23.297 INFO [stderr] --> src/reactor/poll_evented2.rs:40:6 Dec 02 01:49:23.297 INFO [stderr] | Dec 02 01:49:23.297 INFO [stderr] 40 | /// [`poll_read_ready`] and [`poll_write_ready`]. These functions return the Dec 02 01:49:23.297 INFO [stderr] | ^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Dec 02 01:49:23.297 INFO [stderr] | Dec 02 01:49:23.297 INFO [stderr] note: lint level defined here Dec 02 01:49:23.297 INFO [stderr] --> src/lib.rs:94:9 Dec 02 01:49:23.297 INFO [stderr] | Dec 02 01:49:23.297 INFO [stderr] 94 | #![deny(warnings)] Dec 02 01:49:23.298 INFO [stderr] | ^^^^^^^^ Dec 02 01:49:23.298 INFO [stderr] = note: #[deny(intra_doc_link_resolution_failure)] implied by #[deny(warnings)] Dec 02 01:49:23.298 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Dec 02 01:49:23.298 INFO [stderr] Dec 02 01:49:23.298 INFO [stderr] error: `[poll_write_ready]` cannot be resolved, ignoring it... Dec 02 01:49:23.298 INFO [stderr] --> src/reactor/poll_evented2.rs:40:30 Dec 02 01:49:23.298 INFO [stderr] | Dec 02 01:49:23.298 INFO [stderr] 40 | /// [`poll_read_ready`] and [`poll_write_ready`]. These functions return the Dec 02 01:49:23.298 INFO [stderr] | ^^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Dec 02 01:49:23.298 INFO [stderr] | Dec 02 01:49:23.298 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Dec 02 01:49:23.298 INFO [stderr] Dec 02 01:49:23.298 INFO [stderr] error: `[poll_read_ready]` cannot be resolved, ignoring it... Dec 02 01:49:23.298 INFO [stderr] --> src/reactor/poll_evented2.rs:42:6 Dec 02 01:49:23.298 INFO [stderr] | Dec 02 01:49:23.298 INFO [stderr] 42 | /// [`poll_read_ready`] indicates read readiness, immediately calling Dec 02 01:49:23.298 INFO [stderr] | ^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Dec 02 01:49:23.298 INFO [stderr] | Dec 02 01:49:23.298 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Dec 02 01:49:23.298 INFO [stderr] Dec 02 01:49:23.298 INFO [stderr] error: `[poll_read_ready]` cannot be resolved, ignoring it... Dec 02 01:49:23.298 INFO [stderr] --> src/reactor/poll_evented2.rs:43:6 Dec 02 01:49:23.298 INFO [stderr] | Dec 02 01:49:23.298 INFO [stderr] 43 | /// [`poll_read_ready`] again will also indicate read readiness. Dec 02 01:49:23.298 INFO [stderr] | ^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Dec 02 01:49:23.298 INFO [stderr] | Dec 02 01:49:23.298 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Dec 02 01:49:23.298 INFO [stderr] Dec 02 01:49:23.298 INFO [stderr] error: `[clear_read_ready]` cannot be resolved, ignoring it... Dec 02 01:49:23.298 INFO [stderr] --> src/reactor/poll_evented2.rs:46:53 Dec 02 01:49:23.298 INFO [stderr] | Dec 02 01:49:23.298 INFO [stderr] 46 | /// resource not being ready, the caller must call [`clear_read_ready`] or Dec 02 01:49:23.298 INFO [stderr] | ^^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Dec 02 01:49:23.298 INFO [stderr] | Dec 02 01:49:23.298 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Dec 02 01:49:23.298 INFO [stderr] Dec 02 01:49:23.298 INFO [stderr] error: `[clear_write_ready]` cannot be resolved, ignoring it... Dec 02 01:49:23.298 INFO [stderr] --> src/reactor/poll_evented2.rs:47:6 Dec 02 01:49:23.298 INFO [stderr] | Dec 02 01:49:23.298 INFO [stderr] 47 | /// [`clear_write_ready`]. This clears the readiness state until a new readiness Dec 02 01:49:23.298 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Dec 02 01:49:23.298 INFO [stderr] | Dec 02 01:49:23.298 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Dec 02 01:49:23.298 INFO [stderr] Dec 02 01:49:23.298 INFO [stderr] error: `[poll_read_ready]` cannot be resolved, ignoring it... Dec 02 01:49:23.298 INFO [stderr] --> src/reactor/poll_evented2.rs:51:54 Dec 02 01:49:23.298 INFO [stderr] | Dec 02 01:49:23.298 INFO [stderr] 51 | /// [`TcpListener`] implements poll_accept by using [`poll_read_ready`] and Dec 02 01:49:23.298 INFO [stderr] | ^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Dec 02 01:49:23.298 INFO [stderr] | Dec 02 01:49:23.298 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Dec 02 01:49:23.298 INFO [stderr] Dec 02 01:49:23.298 INFO [stderr] error: `[clear_write_ready]` cannot be resolved, ignoring it... Dec 02 01:49:23.298 INFO [stderr] --> src/reactor/poll_evented2.rs:52:6 Dec 02 01:49:23.298 INFO [stderr] | Dec 02 01:49:23.298 INFO [stderr] 52 | /// [`clear_write_ready`]. Dec 02 01:49:23.298 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Dec 02 01:49:23.298 INFO [stderr] | Dec 02 01:49:23.298 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Dec 02 01:49:23.298 INFO [stderr] Dec 02 01:49:23.403 INFO [stderr] error: Could not document `tokio-core`. Dec 02 01:49:23.403 INFO [stderr] Dec 02 01:49:23.403 INFO [stderr] Caused by: Dec 02 01:49:23.403 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-7fbd539cbc81b032.rmeta --extern futures=/target/debug/deps/libfutures-97ba6a0d0dd511fe.rmeta --extern iovec=/target/debug/deps/libiovec-4a9fae56b7e3f2de.rmeta --extern log=/target/debug/deps/liblog-d19a1083c118ed6a.rmeta --extern mio=/target/debug/deps/libmio-68a04a92bf5023f3.rmeta --extern scoped_tls=/target/debug/deps/libscoped_tls-3a5e0f202077f9df.rmeta --extern tokio=/target/debug/deps/libtokio-72ad0bc4feb27f09.rmeta --extern tokio_executor=/target/debug/deps/libtokio_executor-826e9e8e441e741a.rmeta --extern tokio_io=/target/debug/deps/libtokio_io-f9cfaabb42b3840c.rmeta --extern tokio_reactor=/target/debug/deps/libtokio_reactor-623a5e25347a9399.rmeta --extern tokio_timer=/target/debug/deps/libtokio_timer-2d37118a9e387dd7.rmeta --cap-lints=forbid` (exit code: 1) Dec 02 01:49:23.405 INFO [stderr] su: No module specific data is present Dec 02 01:49:23.703 INFO running `"docker" "inspect" "b8ff35692b2b3e431621af6548aa846e1eec3dad3485f103c79ff9bbaf71fa8d"` Dec 02 01:49:23.812 INFO running `"docker" "rm" "-f" "b8ff35692b2b3e431621af6548aa846e1eec3dad3485f103c79ff9bbaf71fa8d"` Dec 02 01:49:23.923 INFO [stdout] b8ff35692b2b3e431621af6548aa846e1eec3dad3485f103c79ff9bbaf71fa8d