[INFO] fetching crate cadence-with-flush 0.29.1... [INFO] testing cadence-with-flush-0.29.1 against try#8de4c7234dd9b97c9d76b58671343fdbbc9a433e+target=x86_64-unknown-linux-musl for musl_upgrade_1_2_5_with_libc_patch_0 [INFO] extracting crate cadence-with-flush 0.29.1 into /workspace/builds/worker-7-tc1/source [INFO] started tweaking crates.io crate cadence-with-flush 0.29.1 [INFO] finished tweaking crates.io crate cadence-with-flush 0.29.1 [INFO] tweaked toml for crates.io crate cadence-with-flush 0.29.1 written to /workspace/builds/worker-7-tc1/source/Cargo.toml [INFO] validating manifest of crates.io crate cadence-with-flush 0.29.1 on toolchain 8de4c7234dd9b97c9d76b58671343fdbbc9a433e [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate crates.io crate cadence-with-flush 0.29.1 already has a lockfile, it will not be regenerated [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 43a0404dd28c15670d38e480c8a9f8bde918523122ed9c02c8b03b18ac12da27 [INFO] running `Command { std: "docker" "start" "-a" "43a0404dd28c15670d38e480c8a9f8bde918523122ed9c02c8b03b18ac12da27", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "43a0404dd28c15670d38e480c8a9f8bde918523122ed9c02c8b03b18ac12da27", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "43a0404dd28c15670d38e480c8a9f8bde918523122ed9c02c8b03b18ac12da27", kill_on_drop: false }` [INFO] [stdout] 43a0404dd28c15670d38e480c8a9f8bde918523122ed9c02c8b03b18ac12da27 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "build" "--frozen" "--message-format=json" "--target" "x86_64-unknown-linux-musl", kill_on_drop: false }` [INFO] [stdout] 2a7cd97a72bef48444fcb878b721bcd3792a193eee274c54d6635f857ebc07f4 [INFO] running `Command { std: "docker" "start" "-a" "2a7cd97a72bef48444fcb878b721bcd3792a193eee274c54d6635f857ebc07f4", kill_on_drop: false }` [INFO] [stderr] Compiling crossbeam-utils v0.8.8 [INFO] [stderr] Compiling crossbeam-channel v0.5.4 [INFO] [stderr] Compiling cadence-with-flush v0.29.1 (/opt/rustwide/workdir) [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:269:29 [INFO] [stdout] | [INFO] [stdout] 269 | fn count_with_tags<'a>(&'a self, key: &'a str, count: T) -> MetricBuilder<'_, '_, Counter>; [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 269 - fn count_with_tags<'a>(&'a self, key: &'a str, count: T) -> MetricBuilder<'_, '_, Counter>; [INFO] [stdout] 269 + fn count_with_tags<'a>(&'a self, key: &'a str, count: T) -> MetricBuilder<'a, 'a, Counter>; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:284:28 [INFO] [stdout] | [INFO] [stdout] 284 | fn incr_with_tags<'a>(&'a self, key: &'a str) -> MetricBuilder<'_, '_, Counter> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 284 - fn incr_with_tags<'a>(&'a self, key: &'a str) -> MetricBuilder<'_, '_, Counter> { [INFO] [stdout] 284 + fn incr_with_tags<'a>(&'a self, key: &'a str) -> MetricBuilder<'a, 'a, Counter> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:295:28 [INFO] [stdout] | [INFO] [stdout] 295 | fn decr_with_tags<'a>(&'a self, key: &'a str) -> MetricBuilder<'_, '_, Counter> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 295 - fn decr_with_tags<'a>(&'a self, key: &'a str) -> MetricBuilder<'_, '_, Counter> { [INFO] [stdout] 295 + fn decr_with_tags<'a>(&'a self, key: &'a str) -> MetricBuilder<'a, 'a, Counter> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:327:28 [INFO] [stdout] | [INFO] [stdout] 327 | fn time_with_tags<'a>(&'a self, key: &'a str, time: T) -> MetricBuilder<'_, '_, Timer>; [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 327 - fn time_with_tags<'a>(&'a self, key: &'a str, time: T) -> MetricBuilder<'_, '_, Timer>; [INFO] [stdout] 327 + fn time_with_tags<'a>(&'a self, key: &'a str, time: T) -> MetricBuilder<'a, 'a, Timer>; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:356:29 [INFO] [stdout] | [INFO] [stdout] 356 | fn gauge_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Gauge>; [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 356 - fn gauge_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Gauge>; [INFO] [stdout] 356 + fn gauge_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'a, 'a, Gauge>; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:386:29 [INFO] [stdout] | [INFO] [stdout] 386 | fn meter_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Meter>; [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 386 - fn meter_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Meter>; [INFO] [stdout] 386 + fn meter_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'a, 'a, Meter>; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:420:33 [INFO] [stdout] | [INFO] [stdout] 420 | fn histogram_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Histogram>; [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 420 - fn histogram_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Histogram>; [INFO] [stdout] 420 + fn histogram_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'a, 'a, Histogram>; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:450:36 [INFO] [stdout] | [INFO] [stdout] 450 | fn distribution_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Distribution>; [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 450 - fn distribution_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Distribution>; [INFO] [stdout] 450 + fn distribution_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'a, 'a, Distribution>; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:474:27 [INFO] [stdout] | [INFO] [stdout] 474 | fn set_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Set>; [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 474 - fn set_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Set>; [INFO] [stdout] 474 + fn set_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'a, 'a, Set>; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:1005:29 [INFO] [stdout] | [INFO] [stdout] 1005 | fn count_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Counter> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 1005 - fn count_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Counter> { [INFO] [stdout] 1005 + fn count_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'a, 'a, Counter> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:1021:28 [INFO] [stdout] | [INFO] [stdout] 1021 | fn time_with_tags<'a>(&'a self, key: &'a str, time: T) -> MetricBuilder<'_, '_, Timer> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 1021 - fn time_with_tags<'a>(&'a self, key: &'a str, time: T) -> MetricBuilder<'_, '_, Timer> { [INFO] [stdout] 1021 + fn time_with_tags<'a>(&'a self, key: &'a str, time: T) -> MetricBuilder<'a, 'a, Timer> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:1033:29 [INFO] [stdout] | [INFO] [stdout] 1033 | fn gauge_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Gauge> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 1033 - fn gauge_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Gauge> { [INFO] [stdout] 1033 + fn gauge_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'a, 'a, Gauge> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:1045:29 [INFO] [stdout] | [INFO] [stdout] 1045 | fn meter_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Meter> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 1045 - fn meter_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Meter> { [INFO] [stdout] 1045 + fn meter_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'a, 'a, Meter> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:1057:33 [INFO] [stdout] | [INFO] [stdout] 1057 | fn histogram_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Histogram> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 1057 - fn histogram_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Histogram> { [INFO] [stdout] 1057 + fn histogram_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'a, 'a, Histogram> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:1071:36 [INFO] [stdout] | [INFO] [stdout] 1071 | fn distribution_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Distribution> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 1071 - fn distribution_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Distribution> { [INFO] [stdout] 1071 + fn distribution_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'a, 'a, Distribution> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:1084:27 [INFO] [stdout] | [INFO] [stdout] 1084 | fn set_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Set> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 1084 - fn set_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Set> { [INFO] [stdout] 1084 + fn set_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'a, 'a, Set> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/compat.rs:32:37 [INFO] [stdout] | [INFO] [stdout] 32 | fn time_duration_with_tags<'a>(&'a self, key: &'a str, val: Duration) -> MetricBuilder<'_, '_, Timer>; [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | these lifetimes flow to the output the lifetimes get resolved as `'a` [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 32 - fn time_duration_with_tags<'a>(&'a self, key: &'a str, val: Duration) -> MetricBuilder<'_, '_, Timer>; [INFO] [stdout] 32 + fn time_duration_with_tags<'a>(&'a self, key: &'a str, val: Duration) -> MetricBuilder<'a, 'a, Timer>; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/compat.rs:41:33 [INFO] [stdout] | [INFO] [stdout] 41 | fn gauge_f64_with_tags<'a>(&'a self, key: &'a str, val: f64) -> MetricBuilder<'_, '_, Gauge>; [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 41 - fn gauge_f64_with_tags<'a>(&'a self, key: &'a str, val: f64) -> MetricBuilder<'_, '_, Gauge>; [INFO] [stdout] 41 + fn gauge_f64_with_tags<'a>(&'a self, key: &'a str, val: f64) -> MetricBuilder<'a, 'a, Gauge>; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/compat.rs:50:28 [INFO] [stdout] | [INFO] [stdout] 50 | fn mark_with_tags<'a>(&'a self, key: &'a str) -> MetricBuilder<'_, '_, Meter>; [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 50 - fn mark_with_tags<'a>(&'a self, key: &'a str) -> MetricBuilder<'_, '_, Meter>; [INFO] [stdout] 50 + fn mark_with_tags<'a>(&'a self, key: &'a str) -> MetricBuilder<'a, 'a, Meter>; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/compat.rs:58:42 [INFO] [stdout] | [INFO] [stdout] 58 | fn histogram_duration_with_tags<'a>(&'a self, key: &'a str, val: Duration) -> MetricBuilder<'_, '_, Histogram>; [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | these lifetimes flow to the output the lifetimes get resolved as `'a` [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 58 - fn histogram_duration_with_tags<'a>(&'a self, key: &'a str, val: Duration) -> MetricBuilder<'_, '_, Histogram>; [INFO] [stdout] 58 + fn histogram_duration_with_tags<'a>(&'a self, key: &'a str, val: Duration) -> MetricBuilder<'a, 'a, Histogram>; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/compat.rs:62:37 [INFO] [stdout] | [INFO] [stdout] 62 | fn time_duration_with_tags<'a>(&'a self, key: &'a str, val: Duration) -> MetricBuilder<'_, '_, Timer> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | these lifetimes flow to the output the lifetimes get resolved as `'a` [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 62 - fn time_duration_with_tags<'a>(&'a self, key: &'a str, val: Duration) -> MetricBuilder<'_, '_, Timer> { [INFO] [stdout] 62 + fn time_duration_with_tags<'a>(&'a self, key: &'a str, val: Duration) -> MetricBuilder<'a, 'a, Timer> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/compat.rs:66:33 [INFO] [stdout] | [INFO] [stdout] 66 | fn gauge_f64_with_tags<'a>(&'a self, key: &'a str, val: f64) -> MetricBuilder<'_, '_, Gauge> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 66 - fn gauge_f64_with_tags<'a>(&'a self, key: &'a str, val: f64) -> MetricBuilder<'_, '_, Gauge> { [INFO] [stdout] 66 + fn gauge_f64_with_tags<'a>(&'a self, key: &'a str, val: f64) -> MetricBuilder<'a, 'a, Gauge> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/compat.rs:70:28 [INFO] [stdout] | [INFO] [stdout] 70 | fn mark_with_tags<'a>(&'a self, key: &'a str) -> MetricBuilder<'_, '_, Meter> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 70 - fn mark_with_tags<'a>(&'a self, key: &'a str) -> MetricBuilder<'_, '_, Meter> { [INFO] [stdout] 70 + fn mark_with_tags<'a>(&'a self, key: &'a str) -> MetricBuilder<'a, 'a, Meter> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/compat.rs:74:42 [INFO] [stdout] | [INFO] [stdout] 74 | fn histogram_duration_with_tags<'a>(&'a self, key: &'a str, val: Duration) -> MetricBuilder<'_, '_, Histogram> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | these lifetimes flow to the output the lifetimes get resolved as `'a` [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 74 - fn histogram_duration_with_tags<'a>(&'a self, key: &'a str, val: Duration) -> MetricBuilder<'_, '_, Histogram> { [INFO] [stdout] 74 + fn histogram_duration_with_tags<'a>(&'a self, key: &'a str, val: Duration) -> MetricBuilder<'a, 'a, Histogram> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 2.56s [INFO] running `Command { std: "docker" "inspect" "2a7cd97a72bef48444fcb878b721bcd3792a193eee274c54d6635f857ebc07f4", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "2a7cd97a72bef48444fcb878b721bcd3792a193eee274c54d6635f857ebc07f4", kill_on_drop: false }` [INFO] [stdout] 2a7cd97a72bef48444fcb878b721bcd3792a193eee274c54d6635f857ebc07f4 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "test" "--frozen" "--no-run" "--message-format=json" "--target" "x86_64-unknown-linux-musl", kill_on_drop: false }` [INFO] [stdout] 4580cebffa0e80b6c6a057c536080bab4e52be86636e5e0db5aa2f93eb4d1ed4 [INFO] running `Command { std: "docker" "start" "-a" "4580cebffa0e80b6c6a057c536080bab4e52be86636e5e0db5aa2f93eb4d1ed4", kill_on_drop: false }` [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:269:29 [INFO] [stdout] | [INFO] [stdout] 269 | fn count_with_tags<'a>(&'a self, key: &'a str, count: T) -> MetricBuilder<'_, '_, Counter>; [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 269 - fn count_with_tags<'a>(&'a self, key: &'a str, count: T) -> MetricBuilder<'_, '_, Counter>; [INFO] [stdout] 269 + fn count_with_tags<'a>(&'a self, key: &'a str, count: T) -> MetricBuilder<'a, 'a, Counter>; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:284:28 [INFO] [stdout] | [INFO] [stdout] 284 | fn incr_with_tags<'a>(&'a self, key: &'a str) -> MetricBuilder<'_, '_, Counter> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 284 - fn incr_with_tags<'a>(&'a self, key: &'a str) -> MetricBuilder<'_, '_, Counter> { [INFO] [stdout] 284 + fn incr_with_tags<'a>(&'a self, key: &'a str) -> MetricBuilder<'a, 'a, Counter> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:295:28 [INFO] [stdout] | [INFO] [stdout] 295 | fn decr_with_tags<'a>(&'a self, key: &'a str) -> MetricBuilder<'_, '_, Counter> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 295 - fn decr_with_tags<'a>(&'a self, key: &'a str) -> MetricBuilder<'_, '_, Counter> { [INFO] [stdout] 295 + fn decr_with_tags<'a>(&'a self, key: &'a str) -> MetricBuilder<'a, 'a, Counter> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:327:28 [INFO] [stdout] | [INFO] [stdout] 327 | fn time_with_tags<'a>(&'a self, key: &'a str, time: T) -> MetricBuilder<'_, '_, Timer>; [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 327 - fn time_with_tags<'a>(&'a self, key: &'a str, time: T) -> MetricBuilder<'_, '_, Timer>; [INFO] [stdout] 327 + fn time_with_tags<'a>(&'a self, key: &'a str, time: T) -> MetricBuilder<'a, 'a, Timer>; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:356:29 [INFO] [stdout] | [INFO] [stdout] 356 | fn gauge_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Gauge>; [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 356 - fn gauge_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Gauge>; [INFO] [stdout] 356 + fn gauge_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'a, 'a, Gauge>; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:386:29 [INFO] [stdout] | [INFO] [stdout] 386 | fn meter_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Meter>; [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 386 - fn meter_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Meter>; [INFO] [stdout] 386 + fn meter_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'a, 'a, Meter>; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:420:33 [INFO] [stdout] | [INFO] [stdout] 420 | fn histogram_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Histogram>; [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 420 - fn histogram_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Histogram>; [INFO] [stdout] 420 + fn histogram_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'a, 'a, Histogram>; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:450:36 [INFO] [stdout] | [INFO] [stdout] 450 | fn distribution_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Distribution>; [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 450 - fn distribution_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Distribution>; [INFO] [stdout] 450 + fn distribution_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'a, 'a, Distribution>; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:474:27 [INFO] [stdout] | [INFO] [stdout] 474 | fn set_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Set>; [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 474 - fn set_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Set>; [INFO] [stdout] 474 + fn set_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'a, 'a, Set>; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:1005:29 [INFO] [stdout] | [INFO] [stdout] 1005 | fn count_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Counter> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 1005 - fn count_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Counter> { [INFO] [stdout] 1005 + fn count_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'a, 'a, Counter> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:1021:28 [INFO] [stdout] | [INFO] [stdout] 1021 | fn time_with_tags<'a>(&'a self, key: &'a str, time: T) -> MetricBuilder<'_, '_, Timer> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 1021 - fn time_with_tags<'a>(&'a self, key: &'a str, time: T) -> MetricBuilder<'_, '_, Timer> { [INFO] [stdout] 1021 + fn time_with_tags<'a>(&'a self, key: &'a str, time: T) -> MetricBuilder<'a, 'a, Timer> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:1033:29 [INFO] [stdout] | [INFO] [stdout] 1033 | fn gauge_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Gauge> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 1033 - fn gauge_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Gauge> { [INFO] [stdout] 1033 + fn gauge_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'a, 'a, Gauge> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:1045:29 [INFO] [stdout] | [INFO] [stdout] 1045 | fn meter_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Meter> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 1045 - fn meter_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Meter> { [INFO] [stdout] 1045 + fn meter_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'a, 'a, Meter> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:1057:33 [INFO] [stdout] | [INFO] [stdout] 1057 | fn histogram_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Histogram> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 1057 - fn histogram_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Histogram> { [INFO] [stdout] 1057 + fn histogram_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'a, 'a, Histogram> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:1071:36 [INFO] [stdout] | [INFO] [stdout] 1071 | fn distribution_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Distribution> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 1071 - fn distribution_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Distribution> { [INFO] [stdout] 1071 + fn distribution_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'a, 'a, Distribution> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/client.rs:1084:27 [INFO] [stdout] | [INFO] [stdout] 1084 | fn set_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Set> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 1084 - fn set_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'_, '_, Set> { [INFO] [stdout] 1084 + fn set_with_tags<'a>(&'a self, key: &'a str, value: T) -> MetricBuilder<'a, 'a, Set> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/compat.rs:32:37 [INFO] [stdout] | [INFO] [stdout] 32 | fn time_duration_with_tags<'a>(&'a self, key: &'a str, val: Duration) -> MetricBuilder<'_, '_, Timer>; [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | these lifetimes flow to the output the lifetimes get resolved as `'a` [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 32 - fn time_duration_with_tags<'a>(&'a self, key: &'a str, val: Duration) -> MetricBuilder<'_, '_, Timer>; [INFO] [stdout] 32 + fn time_duration_with_tags<'a>(&'a self, key: &'a str, val: Duration) -> MetricBuilder<'a, 'a, Timer>; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling cadence-with-flush v0.29.1 (/opt/rustwide/workdir) [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/compat.rs:41:33 [INFO] [stdout] | [INFO] [stdout] 41 | fn gauge_f64_with_tags<'a>(&'a self, key: &'a str, val: f64) -> MetricBuilder<'_, '_, Gauge>; [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 41 - fn gauge_f64_with_tags<'a>(&'a self, key: &'a str, val: f64) -> MetricBuilder<'_, '_, Gauge>; [INFO] [stdout] 41 + fn gauge_f64_with_tags<'a>(&'a self, key: &'a str, val: f64) -> MetricBuilder<'a, 'a, Gauge>; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/compat.rs:50:28 [INFO] [stdout] | [INFO] [stdout] 50 | fn mark_with_tags<'a>(&'a self, key: &'a str) -> MetricBuilder<'_, '_, Meter>; [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 50 - fn mark_with_tags<'a>(&'a self, key: &'a str) -> MetricBuilder<'_, '_, Meter>; [INFO] [stdout] 50 + fn mark_with_tags<'a>(&'a self, key: &'a str) -> MetricBuilder<'a, 'a, Meter>; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/compat.rs:58:42 [INFO] [stdout] | [INFO] [stdout] 58 | fn histogram_duration_with_tags<'a>(&'a self, key: &'a str, val: Duration) -> MetricBuilder<'_, '_, Histogram>; [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | these lifetimes flow to the output the lifetimes get resolved as `'a` [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 58 - fn histogram_duration_with_tags<'a>(&'a self, key: &'a str, val: Duration) -> MetricBuilder<'_, '_, Histogram>; [INFO] [stdout] 58 + fn histogram_duration_with_tags<'a>(&'a self, key: &'a str, val: Duration) -> MetricBuilder<'a, 'a, Histogram>; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/compat.rs:62:37 [INFO] [stdout] | [INFO] [stdout] 62 | fn time_duration_with_tags<'a>(&'a self, key: &'a str, val: Duration) -> MetricBuilder<'_, '_, Timer> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | these lifetimes flow to the output the lifetimes get resolved as `'a` [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 62 - fn time_duration_with_tags<'a>(&'a self, key: &'a str, val: Duration) -> MetricBuilder<'_, '_, Timer> { [INFO] [stdout] 62 + fn time_duration_with_tags<'a>(&'a self, key: &'a str, val: Duration) -> MetricBuilder<'a, 'a, Timer> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/compat.rs:66:33 [INFO] [stdout] | [INFO] [stdout] 66 | fn gauge_f64_with_tags<'a>(&'a self, key: &'a str, val: f64) -> MetricBuilder<'_, '_, Gauge> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 66 - fn gauge_f64_with_tags<'a>(&'a self, key: &'a str, val: f64) -> MetricBuilder<'_, '_, Gauge> { [INFO] [stdout] 66 + fn gauge_f64_with_tags<'a>(&'a self, key: &'a str, val: f64) -> MetricBuilder<'a, 'a, Gauge> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/compat.rs:70:28 [INFO] [stdout] | [INFO] [stdout] 70 | fn mark_with_tags<'a>(&'a self, key: &'a str) -> MetricBuilder<'_, '_, Meter> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | | the lifetimes get resolved as `'a` [INFO] [stdout] | | these lifetimes flow to the output [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 70 - fn mark_with_tags<'a>(&'a self, key: &'a str) -> MetricBuilder<'_, '_, Meter> { [INFO] [stdout] 70 + fn mark_with_tags<'a>(&'a self, key: &'a str) -> MetricBuilder<'a, 'a, Meter> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/compat.rs:74:42 [INFO] [stdout] | [INFO] [stdout] 74 | fn histogram_duration_with_tags<'a>(&'a self, key: &'a str, val: Duration) -> MetricBuilder<'_, '_, Histogram> { [INFO] [stdout] | ^^ ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | | [INFO] [stdout] | | these lifetimes flow to the output the lifetimes get resolved as `'a` [INFO] [stdout] | these lifetimes flow to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 74 - fn histogram_duration_with_tags<'a>(&'a self, key: &'a str, val: Duration) -> MetricBuilder<'_, '_, Histogram> { [INFO] [stdout] 74 + fn histogram_duration_with_tags<'a>(&'a self, key: &'a str, val: Duration) -> MetricBuilder<'a, 'a, Histogram> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `cadence` [INFO] [stdout] --> examples/arc-wrapped-client.rs:14:5 [INFO] [stdout] | [INFO] [stdout] 14 | use cadence::prelude::*; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `cadence` [INFO] [stdout] --> examples/nop-sink.rs:14:5 [INFO] [stdout] | [INFO] [stdout] 14 | use cadence::prelude::*; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `cadence` [INFO] [stdout] --> examples/arc-wrapped-client.rs:15:5 [INFO] [stdout] | [INFO] [stdout] 15 | use cadence::{NopMetricSink, StatsdClient}; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `cadence` [INFO] [stdout] --> examples/sending-tags.rs:14:5 [INFO] [stdout] | [INFO] [stdout] 14 | use cadence::prelude::*; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `cadence` [INFO] [stdout] --> examples/sending-tags.rs:15:5 [INFO] [stdout] | [INFO] [stdout] 15 | use cadence::{MetricError, NopMetricSink, StatsdClient}; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `cadence` [INFO] [stdout] --> examples/nop-sink.rs:15:5 [INFO] [stdout] | [INFO] [stdout] 15 | use cadence::{NopMetricSink, StatsdClient}; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `cadence` [INFO] [stdout] --> examples/spy-sink.rs:15:5 [INFO] [stdout] | [INFO] [stdout] 15 | use cadence::prelude::*; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `cadence` [INFO] [stdout] --> examples/spy-sink.rs:16:5 [INFO] [stdout] | [INFO] [stdout] 16 | use cadence::{BufferedSpyMetricSink, StatsdClient}; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] Some errors have detailed explanations: E0432, E0433. [INFO] [stdout] [INFO] [stdout] For more information about an error, try `rustc --explain E0432`. [INFO] [stdout] [INFO] [stdout] Some errors have detailed explanations: E0432, E0433. [INFO] [stdout] [INFO] [stdout] For more information about an error, try `rustc --explain E0432`. [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `cadence` [INFO] [stdout] --> tests/alloc-with-tags.rs:1:5 [INFO] [stdout] | [INFO] [stdout] 1 | use cadence::prelude::*; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `cadence` [INFO] [stdout] --> tests/utils.rs:3:5 [INFO] [stdout] | [INFO] [stdout] 3 | use cadence::prelude::*; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `cadence` [INFO] [stdout] --> tests/alloc-with-tags.rs:2:5 [INFO] [stdout] | [INFO] [stdout] 2 | use cadence::{NopMetricSink, QueuingMetricSink, StatsdClient}; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `cadence` [INFO] [stdout] --> tests/utils.rs:4:5 [INFO] [stdout] | [INFO] [stdout] 4 | use cadence::StatsdClient; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `cadence` [INFO] [stdout] --> tests/alloc-no-tags.rs:1:5 [INFO] [stdout] | [INFO] [stdout] 1 | use cadence::prelude::*; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `cadence` [INFO] [stdout] --> tests/utils.rs:3:5 [INFO] [stdout] | [INFO] [stdout] 3 | use cadence::prelude::*; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `cadence` [INFO] [stdout] --> tests/alloc-no-tags.rs:2:5 [INFO] [stdout] | [INFO] [stdout] 2 | use cadence::{NopMetricSink, QueuingMetricSink, StatsdClient}; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `cadence` [INFO] [stdout] --> tests/utils.rs:4:5 [INFO] [stdout] | [INFO] [stdout] 4 | use cadence::StatsdClient; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] Some errors have detailed explanations: E0432, E0433. [INFO] [stdout] [INFO] [stdout] For more information about an error, try `rustc --explain E0432`. [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `cadence` [INFO] [stdout] --> tests/utils.rs:3:5 [INFO] [stdout] | [INFO] [stdout] 3 | use cadence::prelude::*; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `cadence` [INFO] [stdout] --> tests/utils.rs:4:5 [INFO] [stdout] | [INFO] [stdout] 4 | use cadence::StatsdClient; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `cadence-with-flush` (example "sending-tags") due to 2 previous errors [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `cadence` [INFO] [stdout] --> tests/unix.rs:3:5 [INFO] [stdout] | [INFO] [stdout] 3 | use cadence::test::UnixServerHarness; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `cadence` [INFO] [stdout] --> tests/utils.rs:3:5 [INFO] [stdout] | [INFO] [stdout] 3 | use cadence::prelude::*; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `cadence` [INFO] [stdout] --> tests/unix.rs:4:5 [INFO] [stdout] | [INFO] [stdout] 4 | use cadence::{BufferedUnixMetricSink, QueuingMetricSink, StatsdClient, UnixMetricSink}; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `cadence` [INFO] [stdout] --> tests/utils.rs:3:5 [INFO] [stdout] | [INFO] [stdout] 3 | use cadence::prelude::*; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `cadence` [INFO] [stdout] --> tests/spy.rs:1:5 [INFO] [stdout] | [INFO] [stdout] 1 | use cadence::{BufferedSpyMetricSink, SpyMetricSink, StatsdClient}; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `cadence` [INFO] [stdout] --> tests/utils.rs:4:5 [INFO] [stdout] | [INFO] [stdout] 4 | use cadence::StatsdClient; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `cadence` [INFO] [stdout] --> tests/utils.rs:4:5 [INFO] [stdout] | [INFO] [stdout] 4 | use cadence::StatsdClient; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `cadence` [INFO] [stdout] --> examples/value-packing.rs:14:5 [INFO] [stdout] | [INFO] [stdout] 14 | use cadence::prelude::*; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `cadence` [INFO] [stdout] --> tests/utils.rs:3:5 [INFO] [stdout] | [INFO] [stdout] 3 | use cadence::prelude::*; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `cadence-with-flush` (example "nop-sink") due to 2 previous errors [INFO] [stdout] error[E0432]: unresolved import `cadence` [INFO] [stdout] --> tests/udp.rs:1:5 [INFO] [stdout] | [INFO] [stdout] 1 | use cadence::{BufferedUdpMetricSink, QueuingMetricSink, StatsdClient, UdpMetricSink, DEFAULT_PORT}; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `cadence-with-flush` (example "spy-sink") due to 2 previous errors [INFO] [stdout] error[E0432]: unresolved import `cadence` [INFO] [stdout] --> tests/utils.rs:4:5 [INFO] [stdout] | [INFO] [stdout] 4 | use cadence::StatsdClient; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `cadence` [INFO] [stdout] --> examples/simple-sink.rs:14:5 [INFO] [stdout] | [INFO] [stdout] 14 | use cadence::prelude::*; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `cadence` [INFO] [stdout] --> examples/value-packing.rs:15:5 [INFO] [stdout] | [INFO] [stdout] 15 | use cadence::{MetricError, NopMetricSink, StatsdClient}; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `cadence` [INFO] [stdout] --> examples/simple-sink.rs:15:5 [INFO] [stdout] | [INFO] [stdout] 15 | use cadence::{StatsdClient, UdpMetricSink, DEFAULT_PORT}; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `cadence` [INFO] [stdout] --> tests/compat.rs:3:5 [INFO] [stdout] | [INFO] [stdout] 3 | use cadence::prelude::*; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `cadence` [INFO] [stdout] --> examples/custom-value-type.rs:14:5 [INFO] [stdout] | [INFO] [stdout] 14 | use cadence::prelude::*; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `cadence` [INFO] [stdout] --> examples/custom-value-type.rs:13:5 [INFO] [stdout] | [INFO] [stdout] 13 | use cadence::ext::{MetricValue, ToGaugeValue}; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `cadence` [INFO] [stdout] --> examples/custom-value-type.rs:15:5 [INFO] [stdout] | [INFO] [stdout] 15 | use cadence::{MetricResult, NopMetricSink, StatsdClient}; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] Some errors have detailed explanations: E0432, E0433. [INFO] [stdout] [INFO] [stdout] For more information about an error, try `rustc --explain E0432`. [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `cadence` [INFO] [stdout] --> tests/compat.rs:4:5 [INFO] [stdout] | [INFO] [stdout] 4 | use cadence::{Gauge, Histogram, Meter, NopMetricSink, StatsdClient, Timer}; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `cadence` [INFO] [stdout] --> tests/core.rs:1:5 [INFO] [stdout] | [INFO] [stdout] 1 | use cadence::prelude::*; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `cadence` [INFO] [stdout] --> tests/utils.rs:3:5 [INFO] [stdout] | [INFO] [stdout] 3 | use cadence::prelude::*; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `cadence` [INFO] [stdout] --> examples/production-sink.rs:15:5 [INFO] [stdout] | [INFO] [stdout] 15 | use cadence::prelude::*; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `cadence` [INFO] [stdout] --> examples/production-sink.rs:16:5 [INFO] [stdout] | [INFO] [stdout] 16 | use cadence::{BufferedUdpMetricSink, QueuingMetricSink, StatsdClient, DEFAULT_PORT}; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `cadence` [INFO] [stdout] --> tests/core.rs:2:5 [INFO] [stdout] | [INFO] [stdout] 2 | use cadence::{Counter, Gauge, Histogram, Meter, NopMetricSink, StatsdClient, Timer}; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `cadence` [INFO] [stdout] --> tests/utils.rs:4:5 [INFO] [stdout] | [INFO] [stdout] 4 | use cadence::StatsdClient; [INFO] [stdout] | ^^^^^^^ use of unresolved module or unlinked crate `cadence` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `cadence`, use `cargo add cadence` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0405]: cannot find trait `MetricClient` in this scope [INFO] [stdout] --> examples/arc-wrapped-client.rs:24:22 [INFO] [stdout] | [INFO] [stdout] 24 | metrics: Arc, [INFO] [stdout] | ^^^^^^^^^^^^ not found in this scope [INFO] [stdout] | [INFO] [stdout] help: consider importing this trait [INFO] [stdout] | [INFO] [stdout] 14 + use cadence_with_flush::MetricClient; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] Some errors have detailed explanations: E0405, E0432, E0433. [INFO] [stdout] [INFO] [stdout] For more information about an error, try `rustc --explain E0405`. [INFO] [stdout] [INFO] [stdout] Some errors have detailed explanations: E0432, E0433. [INFO] [stdout] [INFO] [stdout] For more information about an error, try `rustc --explain E0432`. [INFO] [stdout] [INFO] [stdout] Some errors have detailed explanations: E0432, E0433. [INFO] [stdout] [INFO] [stdout] For more information about an error, try `rustc --explain E0432`. [INFO] [stdout] [INFO] [stderr] error: could not compile `cadence-with-flush` (example "custom-value-type") due to 3 previous errors [INFO] [stderr] error: could not compile `cadence-with-flush` (example "simple-sink") due to 2 previous errors [INFO] [stderr] error: could not compile `cadence-with-flush` (example "value-packing") due to 2 previous errors [INFO] [stderr] error: could not compile `cadence-with-flush` (example "arc-wrapped-client") due to 3 previous errors [INFO] [stdout] Some errors have detailed explanations: E0432, E0433. [INFO] [stdout] [INFO] [stdout] Some errors have detailed explanations: E0432, E0433. [INFO] [stdout] [INFO] [stdout] For more information about an error, try `rustc --explain E0432`. [INFO] [stdout] [INFO] [stdout] For more information about an error, try `rustc --explain E0432`. [INFO] [stdout] [INFO] [stderr] error: could not compile `cadence-with-flush` (test "compat") due to 2 previous errors [INFO] [stdout] Some errors have detailed explanations: E0432, E0433. [INFO] [stdout] [INFO] [stdout] For more information about an error, try `rustc --explain E0432`. [INFO] [stdout] [INFO] [stdout] Some errors have detailed explanations: E0432, E0433. [INFO] [stdout] [INFO] [stdout] For more information about an error, try `rustc --explain E0432`. [INFO] [stdout] [INFO] [stderr] error: could not compile `cadence-with-flush` (example "production-sink") due to 2 previous errors [INFO] [stderr] error: could not compile `cadence-with-flush` (test "alloc-with-tags") due to 4 previous errors [INFO] [stderr] error: could not compile `cadence-with-flush` (test "alloc-no-tags") due to 4 previous errors [INFO] [stdout] Some errors have detailed explanations: E0432, E0433. [INFO] [stdout] [INFO] [stdout] For more information about an error, try `rustc --explain E0432`. [INFO] [stdout] [INFO] [stderr] error: could not compile `cadence-with-flush` (test "spy") due to 3 previous errors [INFO] [stdout] Some errors have detailed explanations: E0432, E0433. [INFO] [stdout] [INFO] [stderr] error: could not compile `cadence-with-flush` (test "utils") due to 2 previous errors [INFO] [stdout] For more information about an error, try `rustc --explain E0432`. [INFO] [stdout] [INFO] [stderr] error: could not compile `cadence-with-flush` (test "unix") due to 4 previous errors [INFO] [stdout] Some errors have detailed explanations: E0432, E0433. [INFO] [stdout] [INFO] [stdout] For more information about an error, try `rustc --explain E0432`. [INFO] [stdout] [INFO] [stdout] Some errors have detailed explanations: E0432, E0433. [INFO] [stdout] [INFO] [stdout] For more information about an error, try `rustc --explain E0432`. [INFO] [stdout] [INFO] [stdout] Some errors have detailed explanations: E0432, E0433. [INFO] [stdout] [INFO] [stdout] For more information about an error, try `rustc --explain E0432`. [INFO] [stdout] [INFO] [stderr] error: could not compile `cadence-with-flush` (test "udp") due to 3 previous errors [INFO] [stderr] error: could not compile `cadence-with-flush` (test "core") due to 4 previous errors [INFO] running `Command { std: "docker" "inspect" "4580cebffa0e80b6c6a057c536080bab4e52be86636e5e0db5aa2f93eb4d1ed4", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "4580cebffa0e80b6c6a057c536080bab4e52be86636e5e0db5aa2f93eb4d1ed4", kill_on_drop: false }` [INFO] [stdout] 4580cebffa0e80b6c6a057c536080bab4e52be86636e5e0db5aa2f93eb4d1ed4