[INFO] fetching crate rucaja 0.4.5... [INFO] testing rucaja-0.4.5 against try#8de4c7234dd9b97c9d76b58671343fdbbc9a433e+target=x86_64-unknown-linux-musl for musl_upgrade_1_2_5_with_libc_patch_0 [INFO] extracting crate rucaja 0.4.5 into /workspace/builds/worker-5-tc1/source [INFO] started tweaking crates.io crate rucaja 0.4.5 [INFO] finished tweaking crates.io crate rucaja 0.4.5 [INFO] tweaked toml for crates.io crate rucaja 0.4.5 written to /workspace/builds/worker-5-tc1/source/Cargo.toml [INFO] validating manifest of crates.io crate rucaja 0.4.5 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] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating crates.io index [INFO] [stderr] Locking 1 package to latest compatible version [INFO] [stderr] Adding jni-sys v0.3.0 (available: v0.4.0) [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] [stderr] warning: no edition set: defaulting to the 2015 edition while the latest is 2024 [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:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 69472e9ee2b50c7873f1855fdfbd845673419b3d3ffdaaea2e44f0ab3b90230a [INFO] running `Command { std: "docker" "start" "-a" "69472e9ee2b50c7873f1855fdfbd845673419b3d3ffdaaea2e44f0ab3b90230a", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "69472e9ee2b50c7873f1855fdfbd845673419b3d3ffdaaea2e44f0ab3b90230a", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "69472e9ee2b50c7873f1855fdfbd845673419b3d3ffdaaea2e44f0ab3b90230a", kill_on_drop: false }` [INFO] [stdout] 69472e9ee2b50c7873f1855fdfbd845673419b3d3ffdaaea2e44f0ab3b90230a [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: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] 2f611b470fd3ed0dec64dc75e8449d6f90d06dc162831c51780a3fe24175c179 [INFO] running `Command { std: "docker" "start" "-a" "2f611b470fd3ed0dec64dc75e8449d6f90d06dc162831c51780a3fe24175c179", kill_on_drop: false }` [INFO] [stderr] warning: no edition set: defaulting to the 2015 edition while the latest is 2024 [INFO] [stderr] Compiling rucaja v0.4.5 (/opt/rustwide/workdir) [INFO] [stderr] Compiling jni-sys v0.3.0 [INFO] [stdout] warning: `extern` declarations without an explicit ABI are deprecated [INFO] [stdout] --> src/jvm.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | extern { [INFO] [stdout] | ^^^^^^ help: explicitly specify the "C" ABI: `extern "C"` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(missing_abi)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmArray, jarray); [INFO] [stdout] | ------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_boolean_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmBooleanArray, jbooleanArray); [INFO] [stdout] | -------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_byte_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmByteArray, jbyteArray); [INFO] [stdout] | -------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_char_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmCharArray, jcharArray); [INFO] [stdout] | -------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_class.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | jvm_wrapper!(JvmClass, jclass); [INFO] [stdout] | ------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_double_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmDoubleArray, jdoubleArray); [INFO] [stdout] | ------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_float_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmFloatArray, jfloatArray); [INFO] [stdout] | ---------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_int_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmIntArray, jintArray); [INFO] [stdout] | ------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_long_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmLongArray, jlongArray); [INFO] [stdout] | -------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_object.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_wrapper!(JvmObject, jobject); [INFO] [stdout] | -------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_object_array.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | jvm_array_wrapper!(JvmObjectArray, jobjectArray); [INFO] [stdout] | ------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_short_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmShortArray, jshortArray); [INFO] [stdout] | ---------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_string.rs:9:1 [INFO] [stdout] | [INFO] [stdout] 9 | jvm_wrapper!(JvmString, jstring); [INFO] [stdout] | -------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_throwable.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_wrapper!(JvmThrowable, jthrowable); [INFO] [stdout] | -------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.40s [INFO] running `Command { std: "docker" "inspect" "2f611b470fd3ed0dec64dc75e8449d6f90d06dc162831c51780a3fe24175c179", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "2f611b470fd3ed0dec64dc75e8449d6f90d06dc162831c51780a3fe24175c179", kill_on_drop: false }` [INFO] [stdout] 2f611b470fd3ed0dec64dc75e8449d6f90d06dc162831c51780a3fe24175c179 [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: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] c3cb4adee097bccf196c2baa8efd10c989728070fa877b059ad3d4b4968bd111 [INFO] running `Command { std: "docker" "start" "-a" "c3cb4adee097bccf196c2baa8efd10c989728070fa877b059ad3d4b4968bd111", kill_on_drop: false }` [INFO] [stderr] warning: no edition set: defaulting to the 2015 edition while the latest is 2024 [INFO] [stdout] warning: `extern` declarations without an explicit ABI are deprecated [INFO] [stdout] --> src/jvm.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | extern { [INFO] [stdout] | ^^^^^^ help: explicitly specify the "C" ABI: `extern "C"` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(missing_abi)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmArray, jarray); [INFO] [stdout] | ------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_boolean_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmBooleanArray, jbooleanArray); [INFO] [stdout] | -------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_byte_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmByteArray, jbyteArray); [INFO] [stdout] | -------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_char_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmCharArray, jcharArray); [INFO] [stdout] | -------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_class.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | jvm_wrapper!(JvmClass, jclass); [INFO] [stdout] | ------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_double_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmDoubleArray, jdoubleArray); [INFO] [stdout] | ------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_float_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmFloatArray, jfloatArray); [INFO] [stdout] | ---------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_int_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmIntArray, jintArray); [INFO] [stdout] | ------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_long_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmLongArray, jlongArray); [INFO] [stdout] | -------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_object.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_wrapper!(JvmObject, jobject); [INFO] [stdout] | -------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_object_array.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | jvm_array_wrapper!(JvmObjectArray, jobjectArray); [INFO] [stdout] | ------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling rucaja v0.4.5 (/opt/rustwide/workdir) [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_short_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmShortArray, jshortArray); [INFO] [stdout] | ---------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_string.rs:9:1 [INFO] [stdout] | [INFO] [stdout] 9 | jvm_wrapper!(JvmString, jstring); [INFO] [stdout] | -------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_throwable.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_wrapper!(JvmThrowable, jthrowable); [INFO] [stdout] | -------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `extern` declarations without an explicit ABI are deprecated [INFO] [stdout] --> src/jvm.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | extern { [INFO] [stdout] | ^^^^^^ help: explicitly specify the "C" ABI: `extern "C"` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(missing_abi)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmArray, jarray); [INFO] [stdout] | ------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_boolean_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmBooleanArray, jbooleanArray); [INFO] [stdout] | -------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_byte_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmByteArray, jbyteArray); [INFO] [stdout] | -------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_char_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmCharArray, jcharArray); [INFO] [stdout] | -------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_class.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | jvm_wrapper!(JvmClass, jclass); [INFO] [stdout] | ------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_double_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmDoubleArray, jdoubleArray); [INFO] [stdout] | ------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_float_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmFloatArray, jfloatArray); [INFO] [stdout] | ---------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_int_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmIntArray, jintArray); [INFO] [stdout] | ------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_long_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmLongArray, jlongArray); [INFO] [stdout] | -------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_object.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_wrapper!(JvmObject, jobject); [INFO] [stdout] | -------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_object_array.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | jvm_array_wrapper!(JvmObjectArray, jobjectArray); [INFO] [stdout] | ------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_short_array.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_array_wrapper!(JvmShortArray, jshortArray); [INFO] [stdout] | ---------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` which comes from the expansion of the macro `jvm_array_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_string.rs:9:1 [INFO] [stdout] | [INFO] [stdout] 9 | jvm_wrapper!(JvmString, jstring); [INFO] [stdout] | -------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/macros_jvm_wrappers.rs:23:49 [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name> { [INFO] [stdout] | ^^^^^^^^^^^^^^ ----------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/jvm_throwable.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | jvm_wrapper!(JvmThrowable, jthrowable); [INFO] [stdout] | -------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `jvm_wrapper` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 23 | pub fn from_jvm_ptr(jvm_attachment: &JvmAttachment, jvm_ptr: $java_type) -> Option<$rust_struct_name<'_>> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: linking with `cc` failed: exit status: 1 [INFO] [stdout] | [INFO] [stdout] = note: "cc" "-m64" "/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/rcrt1.o" "/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/crti.o" "/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/crtbeginS.o" "/tmp/rustcnA2kjU/symbols.o" "<2 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "/opt/rustwide/target/x86_64-unknown-linux-musl/debug/deps/{librucaja-1a05989110c90436.rlib}.rlib" "-ljvm" "/opt/rustwide/target/x86_64-unknown-linux-musl/debug/deps/{libjni_sys-6e4ea7e6b5a7a190.rlib}.rlib" "/lib/rustlib/x86_64-unknown-linux-musl/lib/{libstd-*,libpanic_unwind-*,libobject-*,libmemchr-*,libaddr2line-*,libgimli-*,librustc_demangle-*,libstd_detect-*,libhashbrown-*,librustc_std_workspace_alloc-*,libminiz_oxide-*,libadler2-*,libunwind-*}.rlib" "-lunwind" "/lib/rustlib/x86_64-unknown-linux-musl/lib/{libcfg_if-*,liblibc-*}.rlib" "-lc" "/lib/rustlib/x86_64-unknown-linux-musl/lib/{librustc_std_workspace_core-*,liballoc-*,libcore-*,libcompiler_builtins-*}.rlib" "-L" "/tmp/rustcnA2kjU/raw-dylibs" "-Wl,-Bdynamic" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-nostartfiles" "-L" "/usr/lib/jvm/default-java/jre/lib/server" "-L" "/usr/lib/jvm/default-java/jre/lib/amd64/server" "-L" "/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained" "-L" "/lib/rustlib/x86_64-unknown-linux-musl/lib" "-o" "/opt/rustwide/target/x86_64-unknown-linux-musl/debug/examples/main-7ec36317ccf435c1" "-Wl,--gc-sections" "-static-pie" "-Wl,-z,relro,-z,now" "-nodefaultlibs" "/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/crtendS.o" "/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/crtn.o" [INFO] [stdout] = note: some arguments are omitted. use `--verbose` to show all linker arguments [INFO] [stdout] = note: /usr/bin/ld: cannot find -ljvm: No such file or directory [INFO] [stdout] collect2: error: ld returned 1 exit status [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `rucaja` (example "main") due to 1 previous error [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] [stdout] error: linking with `cc` failed: exit status: 1 [INFO] [stdout] | [INFO] [stdout] = note: "cc" "-m64" "/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/rcrt1.o" "/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/crti.o" "/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/crtbeginS.o" "/tmp/rustcd0kmSI/symbols.o" "<2 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "/lib/rustlib/x86_64-unknown-linux-musl/lib/{libtest-*,libgetopts-*,libunicode_width-*,librustc_std_workspace_std-*}.rlib" "/opt/rustwide/target/x86_64-unknown-linux-musl/debug/deps/{librucaja-1a05989110c90436.rlib}.rlib" "-ljvm" "/opt/rustwide/target/x86_64-unknown-linux-musl/debug/deps/{libjni_sys-6e4ea7e6b5a7a190.rlib}.rlib" "/lib/rustlib/x86_64-unknown-linux-musl/lib/{libstd-*,libpanic_unwind-*,libobject-*,libmemchr-*,libaddr2line-*,libgimli-*,librustc_demangle-*,libstd_detect-*,libhashbrown-*,librustc_std_workspace_alloc-*,libminiz_oxide-*,libadler2-*,libunwind-*}.rlib" "-lunwind" "/lib/rustlib/x86_64-unknown-linux-musl/lib/{libcfg_if-*,liblibc-*}.rlib" "-lc" "/lib/rustlib/x86_64-unknown-linux-musl/lib/{librustc_std_workspace_core-*,liballoc-*,libcore-*,libcompiler_builtins-*}.rlib" "-L" "/tmp/rustcd0kmSI/raw-dylibs" "-Wl,-Bdynamic" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-nostartfiles" "-L" "/usr/lib/jvm/default-java/jre/lib/server" "-L" "/usr/lib/jvm/default-java/jre/lib/amd64/server" "-L" "/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained" "-L" "/lib/rustlib/x86_64-unknown-linux-musl/lib" "-o" "/opt/rustwide/target/x86_64-unknown-linux-musl/debug/deps/jvm_array-256123764a289f10" "-Wl,--gc-sections" "-static-pie" "-Wl,-z,relro,-z,now" "-nodefaultlibs" "/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/crtendS.o" "/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/crtn.o" [INFO] [stdout] = note: some arguments are omitted. use `--verbose` to show all linker arguments [INFO] [stdout] = note: /usr/bin/ld: cannot find -ljvm: No such file or directory [INFO] [stdout] collect2: error: ld returned 1 exit status [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `rucaja` (test "jvm_array") due to 1 previous error [INFO] [stdout] error: linking with `cc` failed: exit status: 1 [INFO] [stdout] | [INFO] [stdout] = note: "cc" "-m64" "/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/rcrt1.o" "/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/crti.o" "/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/crtbeginS.o" "/tmp/rustcAmb1k0/symbols.o" "<2 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "/lib/rustlib/x86_64-unknown-linux-musl/lib/{libtest-*,libgetopts-*,libunicode_width-*,librustc_std_workspace_std-*}.rlib" "/opt/rustwide/target/x86_64-unknown-linux-musl/debug/deps/{librucaja-1a05989110c90436.rlib}.rlib" "-ljvm" "/opt/rustwide/target/x86_64-unknown-linux-musl/debug/deps/{libjni_sys-6e4ea7e6b5a7a190.rlib}.rlib" "/lib/rustlib/x86_64-unknown-linux-musl/lib/{libstd-*,libpanic_unwind-*,libobject-*,libmemchr-*,libaddr2line-*,libgimli-*,librustc_demangle-*,libstd_detect-*,libhashbrown-*,librustc_std_workspace_alloc-*,libminiz_oxide-*,libadler2-*,libunwind-*}.rlib" "-lunwind" "/lib/rustlib/x86_64-unknown-linux-musl/lib/{libcfg_if-*,liblibc-*}.rlib" "-lc" "/lib/rustlib/x86_64-unknown-linux-musl/lib/{librustc_std_workspace_core-*,liballoc-*,libcore-*,libcompiler_builtins-*}.rlib" "-L" "/tmp/rustcAmb1k0/raw-dylibs" "-Wl,-Bdynamic" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-nostartfiles" "-L" "/usr/lib/jvm/default-java/jre/lib/server" "-L" "/usr/lib/jvm/default-java/jre/lib/amd64/server" "-L" "/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained" "-L" "/lib/rustlib/x86_64-unknown-linux-musl/lib" "-o" "/opt/rustwide/target/x86_64-unknown-linux-musl/debug/deps/jvm_integers-f917c3dee9dd751f" "-Wl,--gc-sections" "-static-pie" "-Wl,-z,relro,-z,now" "-nodefaultlibs" "/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/crtendS.o" "/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/crtn.o" [INFO] [stdout] = note: some arguments are omitted. use `--verbose` to show all linker arguments [INFO] [stdout] = note: /usr/bin/ld: cannot find -ljvm: No such file or directory [INFO] [stdout] collect2: error: ld returned 1 exit status [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `rucaja` (test "jvm_integers") due to 1 previous error [INFO] [stdout] error: linking with `cc` failed: exit status: 1 [INFO] [stdout] | [INFO] [stdout] = note: "cc" "-m64" "/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/rcrt1.o" "/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/crti.o" "/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/crtbeginS.o" "/tmp/rustcebl0DQ/symbols.o" "<2 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "-ljvm" "/lib/rustlib/x86_64-unknown-linux-musl/lib/{libtest-*,libgetopts-*,libunicode_width-*,librustc_std_workspace_std-*}.rlib" "/opt/rustwide/target/x86_64-unknown-linux-musl/debug/deps/{libjni_sys-6e4ea7e6b5a7a190.rlib}.rlib" "/lib/rustlib/x86_64-unknown-linux-musl/lib/{libstd-*,libpanic_unwind-*,libobject-*,libmemchr-*,libaddr2line-*,libgimli-*,librustc_demangle-*,libstd_detect-*,libhashbrown-*,librustc_std_workspace_alloc-*,libminiz_oxide-*,libadler2-*,libunwind-*}.rlib" "-lunwind" "/lib/rustlib/x86_64-unknown-linux-musl/lib/{libcfg_if-*,liblibc-*}.rlib" "-lc" "/lib/rustlib/x86_64-unknown-linux-musl/lib/{librustc_std_workspace_core-*,liballoc-*,libcore-*,libcompiler_builtins-*}.rlib" "-L" "/tmp/rustcebl0DQ/raw-dylibs" "-Wl,-Bdynamic" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-nostartfiles" "-L" "/usr/lib/jvm/default-java/jre/lib/server" "-L" "/usr/lib/jvm/default-java/jre/lib/amd64/server" "-L" "/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained" "-L" "/lib/rustlib/x86_64-unknown-linux-musl/lib" "-o" "/opt/rustwide/target/x86_64-unknown-linux-musl/debug/deps/rucaja-600e0d0ef6647e41" "-Wl,--gc-sections" "-static-pie" "-Wl,-z,relro,-z,now" "-nodefaultlibs" "/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/crtendS.o" "/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/crtn.o" [INFO] [stdout] = note: some arguments are omitted. use `--verbose` to show all linker arguments [INFO] [stdout] = note: /usr/bin/ld: cannot find -ljvm: No such file or directory [INFO] [stdout] collect2: error: ld returned 1 exit status [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `rucaja` (lib test) due to 1 previous error; 15 warnings emitted [INFO] running `Command { std: "docker" "inspect" "c3cb4adee097bccf196c2baa8efd10c989728070fa877b059ad3d4b4968bd111", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "c3cb4adee097bccf196c2baa8efd10c989728070fa877b059ad3d4b4968bd111", kill_on_drop: false }` [INFO] [stdout] c3cb4adee097bccf196c2baa8efd10c989728070fa877b059ad3d4b4968bd111