Dec 02 00:52:35.554 INFO documenting wurl-0.1.0 against try#f86f76f89ea2b1ccbfb3741962ec2029d878a389 for pr-55318-1
Dec 02 00:52:35.555 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55318-1/worker-5/try#f86f76f89ea2b1ccbfb3741962ec2029d878a389:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/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 00:52:36.031 INFO [stdout] 4fb1a5dd6290bba39ccc845a02dc39b8592120db108b201181dbbaa8c3f90333
Dec 02 00:52:36.033 INFO running `"docker" "start" "-a" "4fb1a5dd6290bba39ccc845a02dc39b8592120db108b201181dbbaa8c3f90333"`
Dec 02 00:52:38.268 INFO [stderr] usermod: no changes
Dec 02 00:52:38.380 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 02 00:52:38.380 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 02 00:52:38.380 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 02 00:52:38.380 INFO [stderr] files will be included as a binary target:
Dec 02 00:52:38.380 INFO [stderr] 
Dec 02 00:52:38.380 INFO [stderr] * /source/src/bin/app.rs
Dec 02 00:52:38.380 INFO [stderr] * /source/src/bin/messages.rs
Dec 02 00:52:38.380 INFO [stderr] 
Dec 02 00:52:38.380 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 02 00:52:38.380 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 02 00:52:38.380 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 02 00:52:38.380 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 02 00:52:38.380 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 02 00:52:38.380 INFO [stderr] 
Dec 02 00:52:38.380 INFO [stderr] For more information on this warning you can consult
Dec 02 00:52:38.380 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 02 00:52:38.580 INFO [stderr]    Compiling termcolor v0.3.6
Dec 02 00:52:38.580 INFO [stderr]    Compiling rprompt v1.0.3
Dec 02 00:52:38.580 INFO [stderr]    Compiling iovec v0.1.2
Dec 02 00:52:38.580 INFO [stderr]    Compiling net2 v0.2.33
Dec 02 00:52:38.580 INFO [stderr]    Compiling openssl-sys v0.9.39
Dec 02 00:52:38.580 INFO [stderr]    Compiling chrono v0.4.6
Dec 02 00:52:38.612 INFO [stderr]     Checking stderrlog v0.3.0
Dec 02 00:52:38.612 INFO [stderr]     Checking ws v0.7.9
Dec 02 00:52:41.220 INFO [stderr]    Compiling bytes v0.4.11
Dec 02 00:52:45.048 INFO [stderr]    Compiling openssl v0.10.15
Dec 02 00:52:45.064 INFO [stderr]    Compiling mio v0.6.16
Dec 02 00:52:52.913 INFO [stderr]    Compiling mio-extras v2.0.5
Dec 02 00:53:03.125 INFO [stderr]    Compiling wurl v0.1.0 (/source)
Dec 02 00:53:05.220 INFO [stderr]  Documenting wurl v0.1.0 (/source)
Dec 02 00:53:08.664 INFO [stderr] warning: `[s]` cannot be resolved, ignoring it...
Dec 02 00:53:08.664 INFO [stderr]    --> src/network/handler.rs:208:64
Dec 02 00:53:08.664 INFO [stderr]     |
Dec 02 00:53:08.664 INFO [stderr] 208 | /// Parses an Origin string from a websocket URL, replacing ws[s] with http[s].
Dec 02 00:53:08.664 INFO [stderr]     |                                                                ^ cannot be resolved, ignoring
Dec 02 00:53:08.664 INFO [stderr]     |
Dec 02 00:53:08.664 INFO [stderr]     = note: #[warn(intra_doc_link_resolution_failure)] on by default
Dec 02 00:53:08.664 INFO [stderr]     = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
Dec 02 00:53:08.664 INFO [stderr] 
Dec 02 00:53:08.664 INFO [stderr] warning: `[s]` cannot be resolved, ignoring it...
Dec 02 00:53:08.664 INFO [stderr]    --> src/network/handler.rs:208:77
Dec 02 00:53:08.664 INFO [stderr]     |
Dec 02 00:53:08.664 INFO [stderr] 208 | /// Parses an Origin string from a websocket URL, replacing ws[s] with http[s].
Dec 02 00:53:08.664 INFO [stderr]     |                                                                             ^ cannot be resolved, ignoring
Dec 02 00:53:08.664 INFO [stderr]     |
Dec 02 00:53:08.664 INFO [stderr]     = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
Dec 02 00:53:08.664 INFO [stderr] 
Dec 02 00:53:08.664 INFO [stderr] warning: `[ping]` cannot be resolved, ignoring it...
Dec 02 00:53:08.665 INFO [stderr]   --> src/util/options.rs:49:55
Dec 02 00:53:08.665 INFO [stderr]    |
Dec 02 00:53:08.665 INFO [stderr] 49 |     /// with the type of control frame, for example "[ping]", and further
Dec 02 00:53:08.665 INFO [stderr]    |                                                       ^^^^ cannot be resolved, ignoring
Dec 02 00:53:08.665 INFO [stderr]    |
Dec 02 00:53:08.665 INFO [stderr]    = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
Dec 02 00:53:08.665 INFO [stderr] 
Dec 02 00:53:08.804 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 30.51s
Dec 02 00:53:08.817 INFO [stderr] su: No module specific data is present
Dec 02 00:53:10.405 INFO running `"docker" "inspect" "4fb1a5dd6290bba39ccc845a02dc39b8592120db108b201181dbbaa8c3f90333"`
Dec 02 00:53:10.790 INFO running `"docker" "rm" "-f" "4fb1a5dd6290bba39ccc845a02dc39b8592120db108b201181dbbaa8c3f90333"`
Dec 02 00:53:11.174 INFO [stdout] 4fb1a5dd6290bba39ccc845a02dc39b8592120db108b201181dbbaa8c3f90333