[INFO] cloning repository https://github.com/se7entyse7en/ohmyfpg [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/se7entyse7en/ohmyfpg" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fse7entyse7en%2Fohmyfpg", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fse7entyse7en%2Fohmyfpg'... [INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }` [INFO] [stdout] 2a47d98c9bd079056d864e079adc621c03334133 [INFO] testing se7entyse7en/ohmyfpg against try#028592fec99e54cc92def5a2a849c673b066dd93 for pr-146098 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fse7entyse7en%2Fohmyfpg" "/workspace/builds/worker-2-tc2/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-2-tc2/source'... [INFO] [stderr] done. [INFO] started tweaking git repo https://github.com/se7entyse7en/ohmyfpg [INFO] finished tweaking git repo https://github.com/se7entyse7en/ohmyfpg [INFO] tweaked toml for git repo https://github.com/se7entyse7en/ohmyfpg written to /workspace/builds/worker-2-tc2/source/Cargo.toml [INFO] validating manifest of git repo https://github.com/se7entyse7en/ohmyfpg on toolchain 028592fec99e54cc92def5a2a849c673b066dd93 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+028592fec99e54cc92def5a2a849c673b066dd93" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate git repo https://github.com/se7entyse7en/ohmyfpg 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" "+028592fec99e54cc92def5a2a849c673b066dd93" "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] 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] Blocking waiting for file lock on package cache [INFO] [stderr] Updating crates.io index [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded smallvec v1.8.1 [INFO] [stderr] Downloaded pyo3-asyncio v0.16.0 [INFO] [stderr] Downloaded scram v0.6.0 [INFO] [stderr] Downloaded indoc v1.0.6 [INFO] [stderr] Downloaded unindent v0.1.9 [INFO] [stderr] Downloaded proc-macro2 v1.0.40 [INFO] [stderr] Downloaded target-lexicon v0.12.4 [INFO] [stderr] Downloaded pyo3-build-config v0.16.5 [INFO] [stderr] Downloaded pyo3-macros-backend v0.16.5 [INFO] [stderr] Downloaded pyo3-ffi v0.16.5 [INFO] [stderr] Downloaded unicode-ident v1.0.1 [INFO] [stderr] Downloaded pyo3-macros v0.16.5 [INFO] [stderr] Downloaded pyo3 v0.16.5 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-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:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+028592fec99e54cc92def5a2a849c673b066dd93" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 6a4490e6394abbf8256c285eebadd7b59db6b07bb4c35bbf17b9307f2cb88f62 [INFO] running `Command { std: "docker" "start" "-a" "6a4490e6394abbf8256c285eebadd7b59db6b07bb4c35bbf17b9307f2cb88f62", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "6a4490e6394abbf8256c285eebadd7b59db6b07bb4c35bbf17b9307f2cb88f62", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "6a4490e6394abbf8256c285eebadd7b59db6b07bb4c35bbf17b9307f2cb88f62", kill_on_drop: false }` [INFO] [stdout] 6a4490e6394abbf8256c285eebadd7b59db6b07bb4c35bbf17b9307f2cb88f62 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-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=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:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+028592fec99e54cc92def5a2a849c673b066dd93" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 7c369deb8cb054807a74ea2a214b871c8d40f351e2427a93fffb13a9bb1cc042 [INFO] running `Command { std: "docker" "start" "-a" "7c369deb8cb054807a74ea2a214b871c8d40f351e2427a93fffb13a9bb1cc042", 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] 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.126 [INFO] [stderr] Compiling once_cell v1.12.0 [INFO] [stderr] Compiling proc-macro2 v1.0.40 [INFO] [stderr] Compiling unicode-ident v1.0.1 [INFO] [stderr] Compiling quote v1.0.20 [INFO] [stderr] Compiling syn v1.0.98 [INFO] [stderr] Compiling target-lexicon v0.12.4 [INFO] [stderr] Compiling crossbeam-utils v0.8.11 [INFO] [stderr] Compiling futures-core v0.3.21 [INFO] [stderr] Compiling futures-channel v0.3.21 [INFO] [stderr] Compiling lock_api v0.4.7 [INFO] [stderr] Compiling memoffset v0.6.5 [INFO] [stderr] Compiling crossbeam-epoch v0.9.10 [INFO] [stderr] Compiling futures-task v0.3.21 [INFO] [stderr] Compiling smallvec v1.8.1 [INFO] [stderr] Compiling rayon-core v1.9.3 [INFO] [stderr] Compiling futures-util v0.3.21 [INFO] [stderr] Compiling futures-sink v0.3.21 [INFO] [stderr] Compiling ring v0.16.20 [INFO] [stderr] Compiling futures-io v0.3.21 [INFO] [stderr] Compiling slab v0.4.6 [INFO] [stderr] Compiling rayon v1.5.3 [INFO] [stderr] Compiling aho-corasick v0.7.18 [INFO] [stderr] Compiling either v1.8.0 [INFO] [stderr] Compiling indoc v1.0.6 [INFO] [stderr] Compiling regex-syntax v0.6.26 [INFO] [stderr] Compiling unindent v0.1.9 [INFO] [stderr] Compiling crossbeam-channel v0.5.6 [INFO] [stderr] Compiling crossbeam-deque v0.8.2 [INFO] [stderr] Compiling parking_lot_core v0.9.3 [INFO] [stderr] Compiling getrandom v0.2.7 [INFO] [stderr] Compiling num_cpus v1.13.1 [INFO] [stderr] Compiling signal-hook-registry v1.4.0 [INFO] [stderr] Compiling mio v0.8.4 [INFO] [stderr] Compiling socket2 v0.4.4 [INFO] [stderr] Compiling parking_lot v0.12.1 [INFO] [stderr] Compiling pyo3-build-config v0.16.5 [INFO] [stderr] Compiling rand_core v0.6.3 [INFO] [stderr] Compiling rand_chacha v0.3.1 [INFO] [stderr] Compiling rand v0.8.5 [INFO] [stderr] Compiling regex v1.5.6 [INFO] [stderr] Compiling pyo3-ffi v0.16.5 [INFO] [stderr] Compiling pyo3 v0.16.5 [INFO] [stderr] Compiling scram v0.6.0 [INFO] [stderr] Compiling pyo3-macros-backend v0.16.5 [INFO] [stderr] Compiling futures-macro v0.3.21 [INFO] [stderr] Compiling tokio-macros v1.8.0 [INFO] [stderr] Compiling tokio v1.19.2 [INFO] [stderr] Compiling pyo3-macros v0.16.5 [INFO] [stderr] Compiling futures-executor v0.3.21 [INFO] [stderr] Compiling futures v0.3.21 [INFO] [stderr] Compiling ohmyfpg_core v0.4.0-dev.4 (/opt/rustwide/workdir/ohmyfpg_core) [INFO] [stderr] Compiling pyo3-asyncio v0.16.0 [INFO] [stdout] warning: field `params` is never read [INFO] [stdout] --> ohmyfpg_core/src/client/dsn.rs:13:9 [INFO] [stdout] | [INFO] [stdout] 8 | pub struct Dsn { [INFO] [stdout] | --- field in this struct [INFO] [stdout] ... [INFO] [stdout] 13 | pub params: Option, [INFO] [stdout] | ^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `Dsn` 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] [INFO] [stdout] [INFO] [stderr] Compiling ohmyfpg v0.4.0-dev.4 (/opt/rustwide/workdir/ohmyfpg) [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> ohmyfpg/src/bindings.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | create_exception!(ohmyfpg, PyInvalidDsnError, PyException, "Invalid Dsn."); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [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::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> ohmyfpg/src/bindings.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | create_exception!(ohmyfpg, PyInvalidDsnError, PyException, "Invalid Dsn."); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> ohmyfpg/src/bindings.rs:14:1 [INFO] [stdout] | [INFO] [stdout] 14 | / create_exception!( [INFO] [stdout] 15 | | ohmyfpg, [INFO] [stdout] 16 | | PyUnrecognizedMessageError, [INFO] [stdout] 17 | | PyException, [INFO] [stdout] 18 | | "Unrecognized message." [INFO] [stdout] 19 | | ); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> ohmyfpg/src/bindings.rs:14:1 [INFO] [stdout] | [INFO] [stdout] 14 | / create_exception!( [INFO] [stdout] 15 | | ohmyfpg, [INFO] [stdout] 16 | | PyUnrecognizedMessageError, [INFO] [stdout] 17 | | PyException, [INFO] [stdout] 18 | | "Unrecognized message." [INFO] [stdout] 19 | | ); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> ohmyfpg/src/bindings.rs:20:1 [INFO] [stdout] | [INFO] [stdout] 20 | / create_exception!( [INFO] [stdout] 21 | | ohmyfpg, [INFO] [stdout] 22 | | PyUnexpectedMessageError, [INFO] [stdout] 23 | | PyException, [INFO] [stdout] 24 | | "Unexpected message." [INFO] [stdout] 25 | | ); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> ohmyfpg/src/bindings.rs:20:1 [INFO] [stdout] | [INFO] [stdout] 20 | / create_exception!( [INFO] [stdout] 21 | | ohmyfpg, [INFO] [stdout] 22 | | PyUnexpectedMessageError, [INFO] [stdout] 23 | | PyException, [INFO] [stdout] 24 | | "Unexpected message." [INFO] [stdout] 25 | | ); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> ohmyfpg/src/bindings.rs:26:1 [INFO] [stdout] | [INFO] [stdout] 26 | create_exception!(ohmyfpg, PyServerError, PyException, "Server error."); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> ohmyfpg/src/bindings.rs:26:1 [INFO] [stdout] | [INFO] [stdout] 26 | create_exception!(ohmyfpg, PyServerError, PyException, "Server error."); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> ohmyfpg/src/bindings.rs:30:20 [INFO] [stdout] | [INFO] [stdout] 30 | pub fn connect(py: Python, dsn: String) -> PyResult<&PyAny> { [INFO] [stdout] | ^^^^^^ ^^^^^^ the same lifetime is elided here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is hidden here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 30 | pub fn connect(py: Python<'_>, dsn: String) -> PyResult<&PyAny> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 18.72s [INFO] running `Command { std: "docker" "inspect" "7c369deb8cb054807a74ea2a214b871c8d40f351e2427a93fffb13a9bb1cc042", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "7c369deb8cb054807a74ea2a214b871c8d40f351e2427a93fffb13a9bb1cc042", kill_on_drop: false }` [INFO] [stdout] 7c369deb8cb054807a74ea2a214b871c8d40f351e2427a93fffb13a9bb1cc042 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-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=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:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+028592fec99e54cc92def5a2a849c673b066dd93" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] aa9799f5dfa584e57a065ec791d642d8a60517e32b11c5eaea3407e2d012a870 [INFO] running `Command { std: "docker" "start" "-a" "aa9799f5dfa584e57a065ec791d642d8a60517e32b11c5eaea3407e2d012a870", 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] 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] [stdout] warning: field `params` is never read [INFO] [stdout] --> ohmyfpg_core/src/client/dsn.rs:13:9 [INFO] [stdout] | [INFO] [stdout] 8 | pub struct Dsn { [INFO] [stdout] | --- field in this struct [INFO] [stdout] ... [INFO] [stdout] 13 | pub params: Option, [INFO] [stdout] | ^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `Dsn` 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] [INFO] [stdout] [INFO] [stderr] Compiling ohmyfpg_core v0.4.0-dev.4 (/opt/rustwide/workdir/ohmyfpg_core) [INFO] [stderr] Compiling ohmyfpg v0.4.0-dev.4 (/opt/rustwide/workdir/ohmyfpg) [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> ohmyfpg/src/bindings.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | create_exception!(ohmyfpg, PyInvalidDsnError, PyException, "Invalid Dsn."); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [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::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> ohmyfpg/src/bindings.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | create_exception!(ohmyfpg, PyInvalidDsnError, PyException, "Invalid Dsn."); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> ohmyfpg/src/bindings.rs:14:1 [INFO] [stdout] | [INFO] [stdout] 14 | / create_exception!( [INFO] [stdout] 15 | | ohmyfpg, [INFO] [stdout] 16 | | PyUnrecognizedMessageError, [INFO] [stdout] 17 | | PyException, [INFO] [stdout] 18 | | "Unrecognized message." [INFO] [stdout] 19 | | ); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> ohmyfpg/src/bindings.rs:14:1 [INFO] [stdout] | [INFO] [stdout] 14 | / create_exception!( [INFO] [stdout] 15 | | ohmyfpg, [INFO] [stdout] 16 | | PyUnrecognizedMessageError, [INFO] [stdout] 17 | | PyException, [INFO] [stdout] 18 | | "Unrecognized message." [INFO] [stdout] 19 | | ); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> ohmyfpg/src/bindings.rs:20:1 [INFO] [stdout] | [INFO] [stdout] 20 | / create_exception!( [INFO] [stdout] 21 | | ohmyfpg, [INFO] [stdout] 22 | | PyUnexpectedMessageError, [INFO] [stdout] 23 | | PyException, [INFO] [stdout] 24 | | "Unexpected message." [INFO] [stdout] 25 | | ); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> ohmyfpg/src/bindings.rs:20:1 [INFO] [stdout] | [INFO] [stdout] 20 | / create_exception!( [INFO] [stdout] 21 | | ohmyfpg, [INFO] [stdout] 22 | | PyUnexpectedMessageError, [INFO] [stdout] 23 | | PyException, [INFO] [stdout] 24 | | "Unexpected message." [INFO] [stdout] 25 | | ); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> ohmyfpg/src/bindings.rs:26:1 [INFO] [stdout] | [INFO] [stdout] 26 | create_exception!(ohmyfpg, PyServerError, PyException, "Server error."); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> ohmyfpg/src/bindings.rs:26:1 [INFO] [stdout] | [INFO] [stdout] 26 | create_exception!(ohmyfpg, PyServerError, PyException, "Server error."); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> ohmyfpg/src/bindings.rs:30:20 [INFO] [stdout] | [INFO] [stdout] 30 | pub fn connect(py: Python, dsn: String) -> PyResult<&PyAny> { [INFO] [stdout] | ^^^^^^ ^^^^^^ the same lifetime is elided here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is hidden here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 30 | pub fn connect(py: Python<'_>, dsn: String) -> PyResult<&PyAny> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `params` is never read [INFO] [stdout] --> ohmyfpg_core/src/client/dsn.rs:13:9 [INFO] [stdout] | [INFO] [stdout] 8 | pub struct Dsn { [INFO] [stdout] | --- field in this struct [INFO] [stdout] ... [INFO] [stdout] 13 | pub params: Option, [INFO] [stdout] | ^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `Dsn` 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] [INFO] [stdout] [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 0.88s [INFO] running `Command { std: "docker" "inspect" "aa9799f5dfa584e57a065ec791d642d8a60517e32b11c5eaea3407e2d012a870", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "aa9799f5dfa584e57a065ec791d642d8a60517e32b11c5eaea3407e2d012a870", kill_on_drop: false }` [INFO] [stdout] aa9799f5dfa584e57a065ec791d642d8a60517e32b11c5eaea3407e2d012a870 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-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=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:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+028592fec99e54cc92def5a2a849c673b066dd93" "test" "--frozen", kill_on_drop: false }` [INFO] [stdout] 0d6afc3c2cb2f2a221594f0318a23f2f0784c2c9c8fc87394c18f0196361d501 [INFO] running `Command { std: "docker" "start" "-a" "0d6afc3c2cb2f2a221594f0318a23f2f0784c2c9c8fc87394c18f0196361d501", 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] 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] warning: field `params` is never read [INFO] [stderr] --> ohmyfpg_core/src/client/dsn.rs:13:9 [INFO] [stderr] | [INFO] [stderr] 8 | pub struct Dsn { [INFO] [stderr] | --- field in this struct [INFO] [stderr] ... [INFO] [stderr] 13 | pub params: Option, [INFO] [stderr] | ^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: `Dsn` has a derived impl for the trait `Debug`, but this is intentionally ignored during dead code analysis [INFO] [stderr] = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default [INFO] [stderr] [INFO] [stderr] warning: `ohmyfpg_core` (lib) generated 1 warning [INFO] [stderr] warning: `ohmyfpg_core` (lib test) generated 1 warning (1 duplicate) [INFO] [stderr] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stderr] --> ohmyfpg/src/bindings.rs:13:1 [INFO] [stderr] | [INFO] [stderr] 13 | create_exception!(ohmyfpg, PyInvalidDsnError, PyException, "Invalid Dsn."); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stderr] --> ohmyfpg/src/bindings.rs:13:1 [INFO] [stderr] | [INFO] [stderr] 13 | create_exception!(ohmyfpg, PyInvalidDsnError, PyException, "Invalid Dsn."); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stderr] --> ohmyfpg/src/bindings.rs:14:1 [INFO] [stderr] | [INFO] [stderr] 14 | / create_exception!( [INFO] [stderr] 15 | | ohmyfpg, [INFO] [stderr] 16 | | PyUnrecognizedMessageError, [INFO] [stderr] 17 | | PyException, [INFO] [stderr] 18 | | "Unrecognized message." [INFO] [stderr] 19 | | ); [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stderr] --> ohmyfpg/src/bindings.rs:20:1 [INFO] [stderr] | [INFO] [stderr] 20 | / create_exception!( [INFO] [stderr] 21 | | ohmyfpg, [INFO] [stderr] 22 | | PyUnexpectedMessageError, [INFO] [stderr] 23 | | PyException, [INFO] [stderr] 24 | | "Unexpected message." [INFO] [stderr] 25 | | ); [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stderr] --> ohmyfpg/src/bindings.rs:26:1 [INFO] [stderr] | [INFO] [stderr] 26 | create_exception!(ohmyfpg, PyServerError, PyException, "Server error."); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> ohmyfpg/src/bindings.rs:30:20 [INFO] [stderr] | [INFO] [stderr] 30 | pub fn connect(py: Python, dsn: String) -> PyResult<&PyAny> { [INFO] [stderr] | ^^^^^^ ^^^^^^ the same lifetime is elided here [INFO] [stderr] | | [INFO] [stderr] | the lifetime is hidden here [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 30 | pub fn connect(py: Python<'_>, dsn: String) -> PyResult<&PyAny> { [INFO] [stderr] | ++++ [INFO] [stderr] [INFO] [stderr] warning: `ohmyfpg` (lib test) generated 9 warnings (3 duplicates) (run `cargo fix --lib -p ohmyfpg --tests` to apply 1 suggestion) [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 0.05s [INFO] [stderr] Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/ohmyfpg-42685d2bc510ce23) [INFO] [stdout] [INFO] [stdout] running 0 tests [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stdout] [INFO] [stderr] Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/ohmyfpg_core-e144715692e5a052) [INFO] [stdout] [INFO] [stdout] running 2 tests [INFO] [stdout] test messages::authentication::tests::test_serialize_deserialize ... ok [INFO] [stdout] test messages::startup::tests::test_serialize ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stdout] [INFO] [stderr] Doc-tests ohmyfpg_core [INFO] [stdout] [INFO] [stdout] running 0 tests [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stdout] [INFO] running `Command { std: "docker" "inspect" "0d6afc3c2cb2f2a221594f0318a23f2f0784c2c9c8fc87394c18f0196361d501", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "0d6afc3c2cb2f2a221594f0318a23f2f0784c2c9c8fc87394c18f0196361d501", kill_on_drop: false }` [INFO] [stdout] 0d6afc3c2cb2f2a221594f0318a23f2f0784c2c9c8fc87394c18f0196361d501