[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] checking se7entyse7en/ohmyfpg against master#419b3e2d3e350822550eee0e82eeded4d324d584 for pr-135536 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fse7entyse7en%2Fohmyfpg" "/workspace/builds/worker-1-tc1/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-1-tc1/source'... [INFO] [stderr] done. [INFO] validating manifest of git repo https://github.com/se7entyse7en/ohmyfpg on toolchain 419b3e2d3e350822550eee0e82eeded4d324d584 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+419b3e2d3e350822550eee0e82eeded4d324d584" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [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-1-tc1/source/Cargo.toml [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" "+419b3e2d3e350822550eee0e82eeded4d324d584" "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 scram v0.6.0 [INFO] [stderr] Downloaded pyo3-asyncio v0.16.0 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-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:819108c5571ea2e421544af4d832f968d213c87fbe3707a016657f43d2f853bc" "/opt/rustwide/cargo-home/bin/cargo" "+419b3e2d3e350822550eee0e82eeded4d324d584" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] a1d636f2b0c2e5cd6aec596310ae2c66b9f685e2e64080f2fc0b99c5e3eda9bd [INFO] running `Command { std: "docker" "start" "-a" "a1d636f2b0c2e5cd6aec596310ae2c66b9f685e2e64080f2fc0b99c5e3eda9bd", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "a1d636f2b0c2e5cd6aec596310ae2c66b9f685e2e64080f2fc0b99c5e3eda9bd", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "a1d636f2b0c2e5cd6aec596310ae2c66b9f685e2e64080f2fc0b99c5e3eda9bd", kill_on_drop: false }` [INFO] [stdout] a1d636f2b0c2e5cd6aec596310ae2c66b9f685e2e64080f2fc0b99c5e3eda9bd [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-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:819108c5571ea2e421544af4d832f968d213c87fbe3707a016657f43d2f853bc" "/opt/rustwide/cargo-home/bin/cargo" "+419b3e2d3e350822550eee0e82eeded4d324d584" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] b1bddb6a21fbe616ef12562db8bae3673271325f036923ad55e529fff817916a [INFO] running `Command { std: "docker" "start" "-a" "b1bddb6a21fbe616ef12562db8bae3673271325f036923ad55e529fff817916a", 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] Checking cfg-if v1.0.0 [INFO] [stderr] Compiling autocfg v1.1.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] Checking once_cell v1.12.0 [INFO] [stderr] Checking scopeguard v1.1.0 [INFO] [stderr] Compiling memchr v2.5.0 [INFO] [stderr] Compiling target-lexicon v0.12.4 [INFO] [stderr] Compiling crossbeam-utils v0.8.11 [INFO] [stderr] Compiling memoffset v0.6.5 [INFO] [stderr] Compiling lock_api v0.4.7 [INFO] [stderr] Compiling parking_lot_core v0.9.3 [INFO] [stderr] Compiling crossbeam-epoch v0.9.10 [INFO] [stderr] Checking pin-project-lite v0.2.9 [INFO] [stderr] Compiling log v0.4.17 [INFO] [stderr] Checking smallvec v1.8.1 [INFO] [stderr] Compiling rayon-core v1.9.3 [INFO] [stderr] Compiling pyo3-build-config v0.16.5 [INFO] [stderr] Compiling cc v1.0.73 [INFO] [stderr] Compiling futures-core v0.3.21 [INFO] [stderr] Checking ppv-lite86 v0.2.16 [INFO] [stderr] Checking crossbeam-channel v0.5.6 [INFO] [stderr] Checking num_cpus v1.13.1 [INFO] [stderr] Checking getrandom v0.2.7 [INFO] [stderr] Checking rand_core v0.6.3 [INFO] [stderr] Checking crossbeam-deque v0.8.2 [INFO] [stderr] Checking signal-hook-registry v1.4.0 [INFO] [stderr] Checking socket2 v0.4.4 [INFO] [stderr] Checking parking_lot v0.12.1 [INFO] [stderr] Checking mio v0.8.4 [INFO] [stderr] Checking rand_chacha v0.3.1 [INFO] [stderr] Compiling rayon v1.5.3 [INFO] [stderr] Compiling futures-channel v0.3.21 [INFO] [stderr] Checking spin v0.5.2 [INFO] [stderr] Checking untrusted v0.7.1 [INFO] [stderr] Checking bytes v1.2.1 [INFO] [stderr] Compiling futures-task v0.3.21 [INFO] [stderr] Checking rand v0.8.5 [INFO] [stderr] Compiling ring v0.16.20 [INFO] [stderr] Checking aho-corasick v0.7.18 [INFO] [stderr] Checking futures-sink v0.3.21 [INFO] [stderr] Checking either v1.8.0 [INFO] [stderr] Checking base64 v0.13.0 [INFO] [stderr] Compiling futures-util v0.3.21 [INFO] [stderr] Checking regex-syntax v0.6.26 [INFO] [stderr] Checking pin-utils v0.1.0 [INFO] [stderr] Checking futures-io v0.3.21 [INFO] [stderr] Checking slab v0.4.6 [INFO] [stderr] Compiling indoc v1.0.6 [INFO] [stderr] Checking unindent v0.1.9 [INFO] [stderr] Compiling pyo3-ffi v0.16.5 [INFO] [stderr] Compiling pyo3 v0.16.5 [INFO] [stderr] Checking regex v1.5.6 [INFO] [stderr] Compiling pyo3-macros-backend v0.16.5 [INFO] [stderr] Checking scram v0.6.0 [INFO] [stderr] Compiling tokio-macros v1.8.0 [INFO] [stderr] Compiling futures-macro v0.3.21 [INFO] [stderr] Checking tokio v1.19.2 [INFO] [stderr] Compiling pyo3-macros v0.16.5 [INFO] [stderr] Checking futures-executor v0.3.21 [INFO] [stderr] Checking futures v0.3.21 [INFO] [stderr] Checking ohmyfpg_core v0.4.0-dev.4 (/opt/rustwide/workdir/ohmyfpg_core) [INFO] [stderr] Checking 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)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking 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: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `fmt_debug`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows` [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:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | create_exception!(ohmyfpg, PyInvalidDsnError, PyException, "Invalid Dsn."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `fmt_debug`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows` [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: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: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: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: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: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: 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: 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)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not parse/generate dep info at: /opt/rustwide/target/debug/deps/ohmyfpg_core-b4715fe6c039c549.d [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] failed to write `/opt/rustwide/target/debug/.fingerprint/ohmyfpg_core-b4715fe6c039c549/dep-test-lib-ohmyfpg_core` [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] No space left on device (os error 28) [INFO] running `Command { std: "docker" "inspect" "b1bddb6a21fbe616ef12562db8bae3673271325f036923ad55e529fff817916a", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "b1bddb6a21fbe616ef12562db8bae3673271325f036923ad55e529fff817916a", kill_on_drop: false }` [INFO] [stdout] b1bddb6a21fbe616ef12562db8bae3673271325f036923ad55e529fff817916a