Nov 18 12:12:49.697 INFO testing google-cloudtrace2-cli-1.0.7+20171202 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982
Nov 18 12:12:49.698 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-3/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-alt build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Nov 18 12:12:50.138 INFO [stdout] c51f89aaa83381a4014ea3d8fdc820eb0663ef3f3861f0544a05f1a7ddf8a39d
Nov 18 12:12:50.141 INFO running `"docker" "start" "-a" "c51f89aaa83381a4014ea3d8fdc820eb0663ef3f3861f0544a05f1a7ddf8a39d"`
Nov 18 12:12:51.661 INFO [stderr] usermod: no changes
Nov 18 12:12:51.704 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:12:51.704 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:12:51.704 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:12:51.704 INFO [stderr] files will be included as a binary target:
Nov 18 12:12:51.704 INFO [stderr] 
Nov 18 12:12:51.704 INFO [stderr] * /source/src/main.rs
Nov 18 12:12:51.704 INFO [stderr] 
Nov 18 12:12:51.704 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:12:51.704 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:12:51.704 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:12:51.704 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:12:51.704 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:12:51.704 INFO [stderr] 
Nov 18 12:12:51.704 INFO [stderr] For more information on this warning you can consult
Nov 18 12:12:51.705 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:12:51.705 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `cloudtrace2`,
Nov 18 12:12:51.705 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:12:51.919 INFO [stderr]    Compiling google-cloudtrace2 v1.0.8+20181004
Nov 18 12:12:57.873 INFO [stderr]    Compiling google-cloudtrace2-cli v1.0.7+20171202 (/source)
Nov 18 12:13:02.843 INFO [stderr] error[E0599]: no method named `traces_spans_create` found for type `api::ProjectMethods<'_, hyper::Client, oauth2::Authenticator<oauth2::DefaultAuthenticatorDelegate, cmn::JsonTokenStorage, hyper::Client>>` in the current scope
Nov 18 12:13:02.843 INFO [stderr]    --> src/main.rs:184:44
Nov 18 12:13:02.843 INFO [stderr]     |
Nov 18 12:13:02.843 INFO [stderr] 184 |         let mut call = self.hub.projects().traces_spans_create(request, opt.value_of("name").unwrap_or(""));
Nov 18 12:13:02.843 INFO [stderr]     |                                            ^^^^^^^^^^^^^^^^^^^
Nov 18 12:13:02.843 INFO [stderr]     |
Nov 18 12:13:02.843 INFO [stderr]     = help: did you mean `traces_spans_create_span`?
Nov 18 12:13:02.843 INFO [stderr] 
Nov 18 12:13:03.059 INFO [stderr] error: aborting due to previous error
Nov 18 12:13:03.059 INFO [stderr] 
Nov 18 12:13:03.059 INFO [stderr] For more information about this error, try `rustc --explain E0599`.
Nov 18 12:13:03.085 INFO [stderr] error: Could not compile `google-cloudtrace2-cli`.
Nov 18 12:13:03.085 INFO [stderr] 
Nov 18 12:13:03.085 INFO [stderr] To learn more, run the command again with --verbose.
Nov 18 12:13:03.087 INFO [stderr] su: No module specific data is present
Nov 18 12:13:04.007 INFO running `"docker" "inspect" "c51f89aaa83381a4014ea3d8fdc820eb0663ef3f3861f0544a05f1a7ddf8a39d"`
Nov 18 12:13:04.377 INFO running `"docker" "rm" "-f" "c51f89aaa83381a4014ea3d8fdc820eb0663ef3f3861f0544a05f1a7ddf8a39d"`
Nov 18 12:13:04.743 INFO [stdout] c51f89aaa83381a4014ea3d8fdc820eb0663ef3f3861f0544a05f1a7ddf8a39d