[INFO] cloning repository https://github.com/alisomay/mep [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/alisomay/mep" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Falisomay%2Fmep", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Falisomay%2Fmep'... [INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }` [INFO] [stdout] f9f1248b4fce59496a0321bafe118477526e1fa0 [INFO] checking alisomay/mep against master#bca37a20bd376ce3fd138e7cdee7fe704e0f8814 for pr-139493-3 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Falisomay%2Fmep" "/workspace/builds/worker-5-tc1/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-5-tc1/source'... [INFO] [stderr] done. [INFO] started tweaking git repo https://github.com/alisomay/mep [INFO] finished tweaking git repo https://github.com/alisomay/mep [INFO] tweaked toml for git repo https://github.com/alisomay/mep written to /workspace/builds/worker-5-tc1/source/Cargo.toml [INFO] validating manifest of git repo https://github.com/alisomay/mep on toolchain bca37a20bd376ce3fd138e7cdee7fe704e0f8814 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+bca37a20bd376ce3fd138e7cdee7fe704e0f8814" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate git repo https://github.com/alisomay/mep 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" "+bca37a20bd376ce3fd138e7cdee7fe704e0f8814" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"` [INFO] [stderr] | [INFO] [stderr] = note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest [INFO] [stderr] = note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest [INFO] [stderr] = note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions [INFO] [stderr] Updating git repository `https://github.com/koto-lang/koto` [INFO] [stderr] Updating git repository `https://github.com/alisomay/koto_midi` [INFO] [stderr] Updating crates.io index [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded ppv-lite86 v0.2.14 [INFO] [stderr] Downloaded core-foundation-sys v0.2.3 [INFO] [stderr] Downloaded coremidi-sys v2.0.2 [INFO] [stderr] Downloaded core-foundation v0.2.3 [INFO] [stderr] Downloaded midir v0.7.0 [INFO] [stderr] Downloaded signal-hook-mio v0.2.1 [INFO] [stderr] Downloaded memalloc v0.1.0 [INFO] [stderr] Downloaded coremidi v0.4.0 [INFO] [stderr] Downloaded signal-hook v0.3.10 [INFO] [stderr] Downloaded alsa v0.4.3 [INFO] [stderr] Downloaded crossterm v0.22.1 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-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:aa71247004a7fa38d13ec170f48f06cdedf5bc50b2a8645e56ed7e992e6fa513" "/opt/rustwide/cargo-home/bin/cargo" "+bca37a20bd376ce3fd138e7cdee7fe704e0f8814" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 9d143142488b08cc5855541af539da4d72b8d9a780dfa8e0969121243cecf9c3 [INFO] running `Command { std: "docker" "start" "-a" "9d143142488b08cc5855541af539da4d72b8d9a780dfa8e0969121243cecf9c3", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "9d143142488b08cc5855541af539da4d72b8d9a780dfa8e0969121243cecf9c3", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "9d143142488b08cc5855541af539da4d72b8d9a780dfa8e0969121243cecf9c3", kill_on_drop: false }` [INFO] [stdout] 9d143142488b08cc5855541af539da4d72b8d9a780dfa8e0969121243cecf9c3 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-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:aa71247004a7fa38d13ec170f48f06cdedf5bc50b2a8645e56ed7e992e6fa513" "/opt/rustwide/cargo-home/bin/cargo" "+bca37a20bd376ce3fd138e7cdee7fe704e0f8814" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 33146e0806c6ed3153ea2fb62dc1e86f7bc2dde7f5ef8962d2f78cd1c9d7e161 [INFO] running `Command { std: "docker" "start" "-a" "33146e0806c6ed3153ea2fb62dc1e86f7bc2dde7f5ef8962d2f78cd1c9d7e161", kill_on_drop: false }` [INFO] [stderr] warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"` [INFO] [stderr] | [INFO] [stderr] = note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest [INFO] [stderr] = note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest [INFO] [stderr] = note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions [INFO] [stderr] Compiling libc v0.2.104 [INFO] [stderr] Checking unicode-xid v0.2.2 [INFO] [stderr] Compiling pkg-config v0.3.20 [INFO] [stderr] Checking unicode-segmentation v1.8.0 [INFO] [stderr] Checking ppv-lite86 v0.2.14 [INFO] [stderr] Compiling signal-hook v0.3.10 [INFO] [stderr] Compiling anyhow v1.0.44 [INFO] [stderr] Checking textwrap v0.11.0 [INFO] [stderr] Checking regex v1.5.4 [INFO] [stderr] Checking memalloc v0.1.0 [INFO] [stderr] Checking koto_lexer v0.8.1 (https://github.com/koto-lang/koto?branch=main#8ac89121) [INFO] [stderr] Checking koto_parser v0.8.1 (https://github.com/koto-lang/koto?branch=main#8ac89121) [INFO] [stderr] Compiling alsa-sys v0.3.1 [INFO] [stderr] Checking koto_bytecode v0.8.1 (https://github.com/koto-lang/koto?branch=main#8ac89121) [INFO] [stderr] Checking parking_lot_core v0.8.5 [INFO] [stderr] Checking num_cpus v1.13.0 [INFO] [stderr] Checking getrandom v0.1.16 [INFO] [stderr] Checking signal-hook-registry v1.4.0 [INFO] [stderr] Checking net2 v0.2.37 [INFO] [stderr] Checking iovec v0.1.4 [INFO] [stderr] Checking mio v0.7.14 [INFO] [stderr] Checking inotify-sys v0.1.5 [INFO] [stderr] Checking nix v0.15.0 [INFO] [stderr] Checking filetime v0.2.15 [INFO] [stderr] Checking dirs-sys v0.3.6 [INFO] [stderr] Checking terminal_size v0.1.17 [INFO] [stderr] Checking atty v0.2.14 [INFO] [stderr] Checking dirs v4.0.0 [INFO] [stderr] Checking clap v2.33.3 [INFO] [stderr] Checking rand_core v0.5.1 [INFO] [stderr] Checking console v0.15.0 [INFO] [stderr] Checking inotify v0.7.1 [INFO] [stderr] Checking parking_lot v0.11.2 [INFO] [stderr] Checking mio v0.6.23 [INFO] [stderr] Checking signal-hook-mio v0.2.1 [INFO] [stderr] Checking rand_chacha v0.2.2 [INFO] [stderr] Checking koto_runtime v0.8.1 (https://github.com/koto-lang/koto?branch=main#8ac89121) [INFO] [stderr] Checking crossterm v0.22.1 [INFO] [stderr] Checking rand v0.7.3 [INFO] [stderr] Checking mio-extras v2.0.6 [INFO] [stderr] Checking notify v4.0.17 [INFO] [stderr] Checking koto v0.8.1 (https://github.com/koto-lang/koto?branch=main#8ac89121) [INFO] [stderr] Checking koto_random v0.8.1 (/opt/rustwide/workdir/koto_libraries/random) [INFO] [stderr] Checking koto_midi v0.0.1 (https://github.com/alisomay/koto_midi?branch=main#7cf4579b) [INFO] [stdout] warning: unexpected `cfg` condition name: `panic_on_runtime_error` [INFO] [stdout] --> koto_libraries/random/src/lib.rs:27:18 [INFO] [stdout] | [INFO] [stdout] 27 | _ => runtime_error!("random.generator - expected no arguments, or seed number"), [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::make_runtime_error` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::make_runtime_error` may come from an old version of the `koto_runtime` crate, try updating your dependency with `cargo update -p koto_runtime` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `panic_on_runtime_error` [INFO] [stdout] --> koto_libraries/random/src/lib.rs:80:18 [INFO] [stdout] | [INFO] [stdout] 80 | _ => runtime_error!("random.pick - expected list or range as argument"), [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::make_runtime_error` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::make_runtime_error` may come from an old version of the `koto_runtime` crate, try updating your dependency with `cargo update -p koto_runtime` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `panic_on_runtime_error` [INFO] [stdout] --> koto_libraries/random/src/lib.rs:88:18 [INFO] [stdout] | [INFO] [stdout] 88 | _ => runtime_error!("random.seed - expected number as argument"), [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::make_runtime_error` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::make_runtime_error` may come from an old version of the `koto_runtime` crate, try updating your dependency with `cargo update -p koto_runtime` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `panic_on_runtime_error` [INFO] [stdout] --> koto_libraries/random/src/lib.rs:27:18 [INFO] [stdout] | [INFO] [stdout] 27 | _ => runtime_error!("random.generator - expected no arguments, or seed number"), [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::make_runtime_error` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::make_runtime_error` may come from an old version of the `koto_runtime` crate, try updating your dependency with `cargo update -p koto_runtime` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `panic_on_runtime_error` [INFO] [stdout] --> koto_libraries/random/src/lib.rs:80:18 [INFO] [stdout] | [INFO] [stdout] 80 | _ => runtime_error!("random.pick - expected list or range as argument"), [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::make_runtime_error` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::make_runtime_error` may come from an old version of the `koto_runtime` crate, try updating your dependency with `cargo update -p koto_runtime` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `panic_on_runtime_error` [INFO] [stdout] --> koto_libraries/random/src/lib.rs:88:18 [INFO] [stdout] | [INFO] [stdout] 88 | _ => runtime_error!("random.seed - expected number as argument"), [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::make_runtime_error` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::make_runtime_error` may come from an old version of the `koto_runtime` crate, try updating your dependency with `cargo update -p koto_runtime` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking alsa v0.4.3 [INFO] [stderr] Checking midir v0.7.0 [INFO] [stderr] Checking mep v0.0.1 (/opt/rustwide/workdir/mep) [INFO] [stdout] warning: field `0` is never read [INFO] [stdout] --> mep/src/main.rs:61:18 [INFO] [stdout] | [INFO] [stdout] 61 | NoticeRemove(PathBuf), [INFO] [stdout] | ------------ ^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | field in this variant [INFO] [stdout] | [INFO] [stdout] = note: `WatcherToMainMessage` has a derived impl for the trait `Debug`, but this is intentionally ignored during dead code analysis [INFO] [stdout] = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default [INFO] [stdout] help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field [INFO] [stdout] | [INFO] [stdout] 61 - NoticeRemove(PathBuf), [INFO] [stdout] 61 + NoticeRemove(()), [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `0` is never read [INFO] [stdout] --> mep/src/main.rs:62:12 [INFO] [stdout] | [INFO] [stdout] 62 | Create(PathBuf), [INFO] [stdout] | ------ ^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | field in this variant [INFO] [stdout] | [INFO] [stdout] = note: `WatcherToMainMessage` has a derived impl for the trait `Debug`, but this is intentionally ignored during dead code analysis [INFO] [stdout] help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field [INFO] [stdout] | [INFO] [stdout] 62 - Create(PathBuf), [INFO] [stdout] 62 + Create(()), [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `0` is never read [INFO] [stdout] --> mep/src/main.rs:61:18 [INFO] [stdout] | [INFO] [stdout] 61 | NoticeRemove(PathBuf), [INFO] [stdout] | ------------ ^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | field in this variant [INFO] [stdout] | [INFO] [stdout] = note: `WatcherToMainMessage` has a derived impl for the trait `Debug`, but this is intentionally ignored during dead code analysis [INFO] [stdout] = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default [INFO] [stdout] help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field [INFO] [stdout] | [INFO] [stdout] 61 - NoticeRemove(PathBuf), [INFO] [stdout] 61 + NoticeRemove(()), [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `0` is never read [INFO] [stdout] --> mep/src/main.rs:62:12 [INFO] [stdout] | [INFO] [stdout] 62 | Create(PathBuf), [INFO] [stdout] | ------ ^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | field in this variant [INFO] [stdout] | [INFO] [stdout] = note: `WatcherToMainMessage` has a derived impl for the trait `Debug`, but this is intentionally ignored during dead code analysis [INFO] [stdout] help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field [INFO] [stdout] | [INFO] [stdout] 62 - Create(PathBuf), [INFO] [stdout] 62 + Create(()), [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 7.63s [INFO] running `Command { std: "docker" "inspect" "33146e0806c6ed3153ea2fb62dc1e86f7bc2dde7f5ef8962d2f78cd1c9d7e161", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "33146e0806c6ed3153ea2fb62dc1e86f7bc2dde7f5ef8962d2f78cd1c9d7e161", kill_on_drop: false }` [INFO] [stdout] 33146e0806c6ed3153ea2fb62dc1e86f7bc2dde7f5ef8962d2f78cd1c9d7e161