[INFO] fetching crate yield-progress 0.1.7... [INFO] checking yield-progress-0.1.7 against try#65132f36b923285d5da381c2fbafee6ce899e841 for pr-132712-1 [INFO] extracting crate yield-progress 0.1.7 into /workspace/builds/worker-5-tc2/source [INFO] validating manifest of crates.io crate yield-progress 0.1.7 on toolchain 65132f36b923285d5da381c2fbafee6ce899e841 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+65132f36b923285d5da381c2fbafee6ce899e841" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] started tweaking crates.io crate yield-progress 0.1.7 [INFO] removed 0 missing examples [INFO] finished tweaking crates.io crate yield-progress 0.1.7 [INFO] tweaked toml for crates.io crate yield-progress 0.1.7 written to /workspace/builds/worker-5-tc2/source/Cargo.toml [INFO] crate crates.io crate yield-progress 0.1.7 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" "+65132f36b923285d5da381c2fbafee6ce899e841" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc2/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:4a844ea9eb2546a2d2c7022eacef16ef2e8229c7fbb2c7d4d55a9ceca922f72d" "/opt/rustwide/cargo-home/bin/cargo" "+65132f36b923285d5da381c2fbafee6ce899e841" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] a702492fde5f95877c26224b3c8c4e9aee0ac030bee929d0d0d7ef017ec34c0f [INFO] running `Command { std: "docker" "start" "-a" "a702492fde5f95877c26224b3c8c4e9aee0ac030bee929d0d0d7ef017ec34c0f", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "a702492fde5f95877c26224b3c8c4e9aee0ac030bee929d0d0d7ef017ec34c0f", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "a702492fde5f95877c26224b3c8c4e9aee0ac030bee929d0d0d7ef017ec34c0f", kill_on_drop: false }` [INFO] [stdout] a702492fde5f95877c26224b3c8c4e9aee0ac030bee929d0d0d7ef017ec34c0f [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc2/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=allow" "-e" "RUSTDOCFLAGS=--cap-lints=allow" "-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:4a844ea9eb2546a2d2c7022eacef16ef2e8229c7fbb2c7d4d55a9ceca922f72d" "/opt/rustwide/cargo-home/bin/cargo" "+65132f36b923285d5da381c2fbafee6ce899e841" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] b27ffa7e204fe714926fc21a9ca9c1354287b7b28c1ab3e4b6eea1d7ae79e729 [INFO] running `Command { std: "docker" "start" "-a" "b27ffa7e204fe714926fc21a9ca9c1354287b7b28c1ab3e4b6eea1d7ae79e729", kill_on_drop: false }` [INFO] [stderr] Copying to /tmp/fixit [INFO] [stderr] Running `cargo fix --edition` [INFO] [stderr] Migrating Cargo.toml from 2021 edition to 2024 [INFO] [stderr] Compiling proc-macro2 v1.0.66 [INFO] [stderr] Compiling unicode-ident v1.0.11 [INFO] [stderr] Compiling libc v0.2.147 [INFO] [stderr] Checking pin-project-lite v0.2.12 [INFO] [stderr] Checking yield-progress v0.1.7 (/tmp/fixit) [INFO] [stderr] Migrating src/lib.rs from 2021 edition to 2024 [INFO] [stderr] warning: failed to automatically apply fixes suggested by rustc to crate `yield_progress` [INFO] [stderr] [INFO] [stderr] after fixes were automatically applied the compiler reported errors within these files: [INFO] [stderr] [INFO] [stderr] * src/lib.rs [INFO] [stderr] * src/maybe_sync.rs [INFO] [stderr] [INFO] [stderr] This likely indicates a bug in either rustc or cargo itself, [INFO] [stderr] and we would appreciate a bug report! You're likely to see [INFO] [stderr] a number of compiler warnings after this message which cargo [INFO] [stderr] attempted to fix but failed. If you could open an issue at [INFO] [stderr] https://github.com/rust-lang/rust/issues [INFO] [stderr] quoting the full output of this command we'd be very appreciative! [INFO] [stderr] Note that you may be able to make some more progress in the near-term [INFO] [stderr] fixing code with the `--broken-code` flag [INFO] [stderr] [INFO] [stderr] The following errors were reported: [INFO] [stderr] error: `impl Trait` must mention all type parameters in scope in `use<...>` [INFO] [stderr] --> src/maybe_sync.rs:18:22 [INFO] [stderr] | [INFO] [stderr] 18 | ($t:ty) => { impl Future + Send + 'static + use<> } [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/lib.rs:330:16 [INFO] [stderr] | [INFO] [stderr] 330 | label: impl fmt::Display, [INFO] [stderr] | ----------------- type parameter is implicitly captured by this `impl Trait` [INFO] [stderr] 331 | ) -> maybe_send_impl_future!(Self) { [INFO] [stderr] | ----------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: currently, all type parameters are required to be mentioned in the precise captures list [INFO] [stderr] = note: this error originates in the macro `maybe_send_impl_future` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] error: aborting due to 1 previous error [INFO] [stderr] [INFO] [stderr] Original diagnostics will follow. [INFO] [stderr] [INFO] [stdout] warning: `impl Future + Send + 'static` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/maybe_sync.rs:18:22 [INFO] [stdout] | [INFO] [stdout] 18 | ($t:ty) => { impl Future + Send + 'static } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/lib.rs:246:55 [INFO] [stdout] | [INFO] [stdout] 246 | pub fn progress(&self, progress_fraction: f32) -> maybe_send_impl_future!(()) { [INFO] [stdout] | --------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/lib.rs:246:21 [INFO] [stdout] | [INFO] [stdout] 246 | pub fn progress(&self, progress_fraction: f32) -> maybe_send_impl_future!(()) { [INFO] [stdout] | ^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `maybe_send_impl_future` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit [INFO] [stdout] | [INFO] [stdout] 18 | ($t:ty) => { impl Future + Send + 'static + use<> } [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl Future + Send + 'static` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/maybe_sync.rs:18:22 [INFO] [stdout] | [INFO] [stdout] 18 | ($t:ty) => { impl Future + Send + 'static } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/lib.rs:267:45 [INFO] [stdout] | [INFO] [stdout] 267 | pub fn yield_without_progress(&self) -> maybe_send_impl_future!(()) { [INFO] [stdout] | --------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/lib.rs:267:35 [INFO] [stdout] | [INFO] [stdout] 267 | pub fn yield_without_progress(&self) -> maybe_send_impl_future!(()) { [INFO] [stdout] | ^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `maybe_send_impl_future` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit [INFO] [stdout] | [INFO] [stdout] 18 | ($t:ty) => { impl Future + Send + 'static + use<> } [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl Future + Send + 'static` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/maybe_sync.rs:18:22 [INFO] [stdout] | [INFO] [stdout] 18 | ($t:ty) => { impl Future + Send + 'static } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/lib.rs:331:10 [INFO] [stdout] | [INFO] [stdout] 331 | ) -> maybe_send_impl_future!(Self) { [INFO] [stdout] | ----------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/lib.rs:328:9 [INFO] [stdout] | [INFO] [stdout] 328 | &mut self, [INFO] [stdout] | ^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] note: you could use a `use<...>` bound to explicitly specify captures, but argument-position `impl Trait`s are not nameable [INFO] [stdout] --> src/lib.rs:330:16 [INFO] [stdout] | [INFO] [stdout] 330 | label: impl fmt::Display, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] = note: this warning originates in the macro `maybe_send_impl_future` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling quote v1.0.33 [INFO] [stderr] Checking signal-hook-registry v1.4.1 [INFO] [stderr] Checking mio v0.8.8 [INFO] [stderr] Compiling syn v2.0.29 [INFO] [stderr] Compiling tokio-macros v2.1.0 [INFO] [stderr] Checking tokio v1.32.0 [INFO] [stderr] Migrating tests/tests.rs from 2021 edition to 2024 [INFO] [stderr] warning: failed to automatically apply fixes suggested by rustc to crate `yield_progress` [INFO] [stderr] [INFO] [stderr] after fixes were automatically applied the compiler reported errors within these files: [INFO] [stderr] [INFO] [stderr] * src/lib.rs [INFO] [stderr] * src/maybe_sync.rs [INFO] [stderr] [INFO] [stderr] This likely indicates a bug in either rustc or cargo itself, [INFO] [stderr] and we would appreciate a bug report! You're likely to see [INFO] [stderr] a number of compiler warnings after this message which cargo [INFO] [stderr] attempted to fix but failed. If you could open an issue at [INFO] [stderr] https://github.com/rust-lang/rust/issues [INFO] [stderr] quoting the full output of this command we'd be very appreciative! [INFO] [stderr] Note that you may be able to make some more progress in the near-term [INFO] [stderr] fixing code with the `--broken-code` flag [INFO] [stderr] [INFO] [stderr] The following errors were reported: [INFO] [stderr] error: `impl Trait` must mention all type parameters in scope in `use<...>` [INFO] [stderr] --> src/maybe_sync.rs:18:22 [INFO] [stderr] | [INFO] [stderr] 18 | ($t:ty) => { impl Future + Send + 'static + use<> } [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/lib.rs:330:16 [INFO] [stderr] | [INFO] [stderr] 330 | label: impl fmt::Display, [INFO] [stderr] | ----------------- type parameter is implicitly captured by this `impl Trait` [INFO] [stderr] 331 | ) -> maybe_send_impl_future!(Self) { [INFO] [stderr] | ----------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: currently, all type parameters are required to be mentioned in the precise captures list [INFO] [stderr] = note: this error originates in the macro `maybe_send_impl_future` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] error: aborting due to 1 previous error [INFO] [stderr] [INFO] [stderr] Original diagnostics will follow. [INFO] [stderr] [INFO] [stdout] warning: `impl Future + Send + 'static` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/maybe_sync.rs:18:22 [INFO] [stdout] | [INFO] [stdout] 18 | ($t:ty) => { impl Future + Send + 'static } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/lib.rs:246:55 [INFO] [stdout] | [INFO] [stdout] 246 | pub fn progress(&self, progress_fraction: f32) -> maybe_send_impl_future!(()) { [INFO] [stdout] | --------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/lib.rs:246:21 [INFO] [stdout] | [INFO] [stdout] 246 | pub fn progress(&self, progress_fraction: f32) -> maybe_send_impl_future!(()) { [INFO] [stdout] | ^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `maybe_send_impl_future` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit [INFO] [stdout] | [INFO] [stdout] 18 | ($t:ty) => { impl Future + Send + 'static + use<> } [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl Future + Send + 'static` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/maybe_sync.rs:18:22 [INFO] [stdout] | [INFO] [stdout] 18 | ($t:ty) => { impl Future + Send + 'static } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/lib.rs:267:45 [INFO] [stdout] | [INFO] [stdout] 267 | pub fn yield_without_progress(&self) -> maybe_send_impl_future!(()) { [INFO] [stdout] | --------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/lib.rs:267:35 [INFO] [stdout] | [INFO] [stdout] 267 | pub fn yield_without_progress(&self) -> maybe_send_impl_future!(()) { [INFO] [stdout] | ^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `maybe_send_impl_future` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit [INFO] [stdout] | [INFO] [stdout] 18 | ($t:ty) => { impl Future + Send + 'static + use<> } [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl Future + Send + 'static` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/maybe_sync.rs:18:22 [INFO] [stdout] | [INFO] [stdout] 18 | ($t:ty) => { impl Future + Send + 'static } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/lib.rs:331:10 [INFO] [stdout] | [INFO] [stdout] 331 | ) -> maybe_send_impl_future!(Self) { [INFO] [stdout] | ----------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/lib.rs:328:9 [INFO] [stdout] | [INFO] [stdout] 328 | &mut self, [INFO] [stdout] | ^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] note: you could use a `use<...>` bound to explicitly specify captures, but argument-position `impl Trait`s are not nameable [INFO] [stdout] --> src/lib.rs:330:16 [INFO] [stdout] | [INFO] [stdout] 330 | label: impl fmt::Display, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] = note: this warning originates in the macro `maybe_send_impl_future` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Migrating examples/interactive-cancel.rs from 2021 edition to 2024 [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 4.57s [INFO] [stderr] Running `cargo check` to verify 2024 [INFO] [stderr] Checking yield-progress v0.1.7 (/tmp/fixit) [INFO] [stdout] error[E0597]: `self` does not live long enough [INFO] [stdout] --> src/lib.rs:295:9 [INFO] [stdout] | [INFO] [stdout] 294 | pub fn finish(self) -> maybe_send_impl_future!(()) { [INFO] [stdout] | ---- binding `self` declared here [INFO] [stdout] 295 | self.progress(1.0) [INFO] [stdout] | ^^^^-------------- [INFO] [stdout] | | [INFO] [stdout] | borrowed value does not live long enough [INFO] [stdout] | argument requires that `self` is borrowed for `'static` [INFO] [stdout] 296 | } [INFO] [stdout] | - `self` dropped here while still borrowed [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0597]: `self` does not live long enough [INFO] [stdout] --> src/lib.rs:295:9 [INFO] [stdout] | [INFO] [stdout] 294 | pub fn finish(self) -> maybe_send_impl_future!(()) { [INFO] [stdout] | ---- binding `self` declared here [INFO] [stdout] 295 | self.progress(1.0) [INFO] [stdout] | ^^^^-------------- [INFO] [stdout] | | [INFO] [stdout] | borrowed value does not live long enough [INFO] [stdout] | argument requires that `self` is borrowed for `'static` [INFO] [stdout] 296 | } [INFO] [stdout] | - `self` dropped here while still borrowed [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0597`. [INFO] [stdout] [INFO] [stderr] error: could not compile `yield-progress` (lib) due to 1 previous error [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] [stdout] For more information about this error, try `rustc --explain E0597`. [INFO] [stdout] [INFO] [stderr] error: could not compile `yield-progress` (lib test) due to 1 previous error [INFO] [stderr] error: failed to check after updating to 2024 [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] process didn't exit successfully: `cargo check --frozen --all --all-targets --message-format=json` (exit status: 101) [INFO] running `Command { std: "docker" "inspect" "b27ffa7e204fe714926fc21a9ca9c1354287b7b28c1ab3e4b6eea1d7ae79e729", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "b27ffa7e204fe714926fc21a9ca9c1354287b7b28c1ab3e4b6eea1d7ae79e729", kill_on_drop: false }` [INFO] [stdout] b27ffa7e204fe714926fc21a9ca9c1354287b7b28c1ab3e4b6eea1d7ae79e729