Nov 28 07:10:57.961 INFO documenting wurl-0.1.0 against try#f5a0bd723553ea4b7556bd7087b9f0919cafb483 for pr-55318 Nov 28 07:10:57.963 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55318/worker-7/try#f5a0bd723553ea4b7556bd7087b9f0919cafb483:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/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 07:10:58.370 INFO [stdout] f5075a7e8cfd19a0dc59c01567347f3ede393d3136facdde466e22ce3bd9ad16 Nov 28 07:10:58.373 INFO running `"docker" "start" "-a" "f5075a7e8cfd19a0dc59c01567347f3ede393d3136facdde466e22ce3bd9ad16"` Nov 28 07:11:00.398 INFO [stderr] usermod: no changes Nov 28 07:11:00.499 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 28 07:11:00.499 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 28 07:11:00.499 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 28 07:11:00.499 INFO [stderr] files will be included as a binary target: Nov 28 07:11:00.499 INFO [stderr] Nov 28 07:11:00.499 INFO [stderr] * /source/src/bin/app.rs Nov 28 07:11:00.499 INFO [stderr] * /source/src/bin/messages.rs Nov 28 07:11:00.499 INFO [stderr] Nov 28 07:11:00.499 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 28 07:11:00.499 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 28 07:11:00.499 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 28 07:11:00.499 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 28 07:11:00.499 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 28 07:11:00.499 INFO [stderr] Nov 28 07:11:00.499 INFO [stderr] For more information on this warning you can consult Nov 28 07:11:00.499 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 28 07:11:00.647 INFO [stderr] Compiling rprompt v1.0.3 Nov 28 07:11:00.647 INFO [stderr] Compiling thread_local v0.3.6 Nov 28 07:11:00.653 INFO [stderr] Compiling num-traits v0.2.6 Nov 28 07:11:00.653 INFO [stderr] Compiling net2 v0.2.33 Nov 28 07:11:00.653 INFO [stderr] Compiling atty v0.2.11 Nov 28 07:11:00.653 INFO [stderr] Compiling openssl-sys v0.9.39 Nov 28 07:11:00.653 INFO [stderr] Checking mio-extras v2.0.5 Nov 28 07:11:00.653 INFO [stderr] Checking stderrlog v0.3.0 Nov 28 07:11:02.709 INFO [stderr] Compiling clap v2.32.0 Nov 28 07:11:05.103 INFO [stderr] Checking ws v0.7.9 Nov 28 07:11:05.427 INFO [stderr] Compiling mio v0.6.16 Nov 28 07:11:07.047 INFO [stderr] Compiling openssl v0.10.15 Nov 28 07:11:10.091 INFO [stderr] Compiling num-integer v0.1.39 Nov 28 07:11:14.951 INFO [stderr] Compiling chrono v0.4.6 Nov 28 07:11:36.875 INFO [stderr] Compiling wurl v0.1.0 (/source) Nov 28 07:11:38.819 INFO [stderr] Documenting wurl v0.1.0 (/source) Nov 28 07:11:42.079 INFO [stderr] warning: `[s]` cannot be resolved, ignoring it... Nov 28 07:11:42.079 INFO [stderr] --> src/network/handler.rs:208:64 Nov 28 07:11:42.079 INFO [stderr] | Nov 28 07:11:42.079 INFO [stderr] 208 | /// Parses an Origin string from a websocket URL, replacing ws[s] with http[s]. Nov 28 07:11:42.079 INFO [stderr] | ^ cannot be resolved, ignoring Nov 28 07:11:42.079 INFO [stderr] | Nov 28 07:11:42.079 INFO [stderr] = note: #[warn(intra_doc_link_resolution_failure)] on by default Nov 28 07:11:42.079 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 07:11:42.079 INFO [stderr] Nov 28 07:11:42.079 INFO [stderr] warning: `[s]` cannot be resolved, ignoring it... Nov 28 07:11:42.079 INFO [stderr] --> src/network/handler.rs:208:77 Nov 28 07:11:42.079 INFO [stderr] | Nov 28 07:11:42.079 INFO [stderr] 208 | /// Parses an Origin string from a websocket URL, replacing ws[s] with http[s]. Nov 28 07:11:42.079 INFO [stderr] | ^ cannot be resolved, ignoring Nov 28 07:11:42.079 INFO [stderr] | Nov 28 07:11:42.079 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 07:11:42.079 INFO [stderr] Nov 28 07:11:42.079 INFO [stderr] warning: `[ping]` cannot be resolved, ignoring it... Nov 28 07:11:42.079 INFO [stderr] --> src/util/options.rs:49:55 Nov 28 07:11:42.079 INFO [stderr] | Nov 28 07:11:42.079 INFO [stderr] 49 | /// with the type of control frame, for example "[ping]", and further Nov 28 07:11:42.079 INFO [stderr] | ^^^^ cannot be resolved, ignoring Nov 28 07:11:42.079 INFO [stderr] | Nov 28 07:11:42.079 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 07:11:42.079 INFO [stderr] Nov 28 07:11:42.176 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 41.74s Nov 28 07:11:42.190 INFO [stderr] su: No module specific data is present Nov 28 07:11:43.005 INFO running `"docker" "inspect" "f5075a7e8cfd19a0dc59c01567347f3ede393d3136facdde466e22ce3bd9ad16"` Nov 28 07:11:43.313 INFO running `"docker" "rm" "-f" "f5075a7e8cfd19a0dc59c01567347f3ede393d3136facdde466e22ce3bd9ad16"` Nov 28 07:11:43.611 INFO [stdout] f5075a7e8cfd19a0dc59c01567347f3ede393d3136facdde466e22ce3bd9ad16