[INFO] fetching crate pyonear 0.2.0... [INFO] testing pyonear-0.2.0 against try#2440211fe03bc45c89b6dc1a3df18382ce91e32b for pr-146098-1 [INFO] extracting crate pyonear 0.2.0 into /workspace/builds/worker-0-tc2/source [INFO] started tweaking crates.io crate pyonear 0.2.0 [INFO] finished tweaking crates.io crate pyonear 0.2.0 [INFO] tweaked toml for crates.io crate pyonear 0.2.0 written to /workspace/builds/worker-0-tc2/source/Cargo.toml [INFO] validating manifest of crates.io crate pyonear 0.2.0 on toolchain 2440211fe03bc45c89b6dc1a3df18382ce91e32b [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+2440211fe03bc45c89b6dc1a3df18382ce91e32b" "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" "+2440211fe03bc45c89b6dc1a3df18382ce91e32b" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating crates.io index [INFO] [stderr] Locking 278 packages to latest compatible versions [INFO] [stderr] Adding borsh v0.9.3 (available: v1.5.7) [INFO] [stderr] Adding derive_more v0.99.20 (available: v2.0.1) [INFO] [stderr] Adding ed25519-dalek v1.0.1 (available: v2.2.0) [INFO] [stderr] Adding near-crypto v0.15.0 (available: v0.32.0) [INFO] [stderr] Adding near-primitives v0.15.0 (available: v0.32.0) [INFO] [stderr] Adding near-primitives-core v0.15.0 (available: v0.32.0) [INFO] [stderr] Adding near-vm-errors v0.15.0 (available: v3.1.0) [INFO] [stderr] Adding pyo3 v0.18.3 (available: v0.26.0) [INFO] [stderr] Adding secp256k1 v0.24.3 (available: v0.31.1) [INFO] [stderr] Adding serde_with v2.3.3 (available: v3.14.1) [INFO] [stderr] Adding solders-macros v0.14.4 (available: v0.22.0) [INFO] [stderr] Adding solders-traits v0.14.4 (available: v0.21.0) [INFO] [stderr] Adding zeroize v1.3.0 (available: v1.8.2) [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+2440211fe03bc45c89b6dc1a3df18382ce91e32b" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-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" "+2440211fe03bc45c89b6dc1a3df18382ce91e32b" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 9031881caaca05400cdde89cf3a05300a9954bb01a261ac1c4a5a4c3b2d038cc [INFO] running `Command { std: "docker" "start" "-a" "9031881caaca05400cdde89cf3a05300a9954bb01a261ac1c4a5a4c3b2d038cc", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "9031881caaca05400cdde89cf3a05300a9954bb01a261ac1c4a5a4c3b2d038cc", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "9031881caaca05400cdde89cf3a05300a9954bb01a261ac1c4a5a4c3b2d038cc", kill_on_drop: false }` [INFO] [stdout] 9031881caaca05400cdde89cf3a05300a9954bb01a261ac1c4a5a4c3b2d038cc [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-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" "+2440211fe03bc45c89b6dc1a3df18382ce91e32b" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 6f73374f0f6200ffd442d6305958c63fc2732586804ba93678fc9084efe1c4ff [INFO] running `Command { std: "docker" "start" "-a" "6f73374f0f6200ffd442d6305958c63fc2732586804ba93678fc9084efe1c4ff", kill_on_drop: false }` [INFO] [stderr] Compiling serde_core v1.0.228 [INFO] [stderr] Compiling serde v1.0.228 [INFO] [stderr] Compiling generic-array v0.14.7 [INFO] [stderr] Compiling syn v1.0.109 [INFO] [stderr] Compiling libc v0.2.176 [INFO] [stderr] Compiling crunchy v0.2.4 [INFO] [stderr] Compiling zeroize_derive v1.4.2 [INFO] [stderr] Compiling num-integer v0.1.46 [INFO] [stderr] Compiling semver v1.0.27 [INFO] [stderr] Compiling getrandom v0.1.16 [INFO] [stderr] Compiling rustc_version v0.4.1 [INFO] [stderr] Compiling num-traits v0.2.19 [INFO] [stderr] Compiling toml v0.5.11 [INFO] [stderr] Compiling rand_core v0.5.1 [INFO] [stderr] Compiling zeroize v1.3.0 [INFO] [stderr] Compiling target-lexicon v0.12.16 [INFO] [stderr] Compiling either v1.15.0 [INFO] [stderr] Compiling ahash v0.8.12 [INFO] [stderr] Compiling ahash v0.7.8 [INFO] [stderr] Compiling rand_chacha v0.2.2 [INFO] [stderr] Compiling byteorder v1.5.0 [INFO] [stderr] Compiling wasm-bindgen-shared v0.2.104 [INFO] [stderr] Compiling jobserver v0.1.34 [INFO] [stderr] Compiling winnow v0.7.13 [INFO] [stderr] Compiling pyo3-build-config v0.18.3 [INFO] [stderr] Compiling cc v1.2.39 [INFO] [stderr] Compiling num-bigint v0.4.6 [INFO] [stderr] Compiling digest v0.9.0 [INFO] [stderr] Compiling proc-macro-crate v0.1.5 [INFO] [stderr] Compiling rand v0.7.3 [INFO] [stderr] Compiling hashbrown v0.11.2 [INFO] [stderr] Compiling ark-std v0.4.0 [INFO] [stderr] Compiling toml_datetime v0.7.2 [INFO] [stderr] Compiling subtle v2.6.1 [INFO] [stderr] Compiling hashbrown v0.13.2 [INFO] [stderr] Compiling libsecp256k1-core v0.2.2 [INFO] [stderr] Compiling itertools v0.10.5 [INFO] [stderr] Compiling toml_parser v1.0.3 [INFO] [stderr] Compiling signature v1.6.4 [INFO] [stderr] Compiling block-buffer v0.10.4 [INFO] [stderr] Compiling crypto-common v0.1.6 [INFO] [stderr] Compiling digest v0.10.7 [INFO] [stderr] Compiling crypto-mac v0.8.0 [INFO] [stderr] Compiling borsh-schema-derive-internal v0.9.3 [INFO] [stderr] Compiling borsh-derive-internal v0.9.3 [INFO] [stderr] Compiling block-buffer v0.9.0 [INFO] [stderr] Compiling toml_edit v0.23.6 [INFO] [stderr] Compiling sha2 v0.9.9 [INFO] [stderr] Compiling sha2 v0.10.9 [INFO] [stderr] Compiling curve25519-dalek v3.2.1 [INFO] [stderr] Compiling bumpalo v3.19.0 [INFO] [stderr] Compiling arrayref v0.3.9 [INFO] [stderr] Compiling darling_core v0.20.11 [INFO] [stderr] Compiling hmac v0.8.1 [INFO] [stderr] Compiling wasm-bindgen-backend v0.2.104 [INFO] [stderr] Compiling ed25519 v1.5.3 [INFO] [stderr] Compiling libsecp256k1-gen-ecmult v0.2.1 [INFO] [stderr] Compiling libsecp256k1-gen-genmult v0.2.1 [INFO] [stderr] Compiling solana-frozen-abi-macro v1.18.26 [INFO] [stderr] Compiling bitmaps v2.1.0 [INFO] [stderr] Compiling im v15.1.0 [INFO] [stderr] Compiling proc-macro-crate v3.4.0 [INFO] [stderr] Compiling borsh v1.5.7 [INFO] [stderr] Compiling ed25519-dalek v1.0.1 [INFO] [stderr] Compiling serde_json v1.0.145 [INFO] [stderr] Compiling libsecp256k1 v0.6.0 [INFO] [stderr] Compiling rayon v1.11.0 [INFO] [stderr] Compiling pyo3-ffi v0.18.3 [INFO] [stderr] Compiling borsh-derive-internal v0.10.4 [INFO] [stderr] Compiling sized-chunks v0.6.5 [INFO] [stderr] Compiling borsh-schema-derive-internal v0.10.4 [INFO] [stderr] Compiling secp256k1-sys v0.6.1 [INFO] [stderr] Compiling wasm-bindgen-macro-support v0.2.104 [INFO] [stderr] Compiling blake3 v1.8.2 [INFO] [stderr] Compiling solana-frozen-abi v1.18.26 [INFO] [stderr] Compiling wasm-bindgen v0.2.104 [INFO] [stderr] Compiling rand_xoshiro v0.6.0 [INFO] [stderr] Compiling memoffset v0.9.1 [INFO] [stderr] Compiling num-bigint v0.3.3 [INFO] [stderr] Compiling ark-serialize-derive v0.4.2 [INFO] [stderr] Compiling borsh-derive v0.9.3 [INFO] [stderr] Compiling derivative v2.2.0 [INFO] [stderr] Compiling ark-serialize v0.4.2 [INFO] [stderr] Compiling ark-ff-asm v0.4.2 [INFO] [stderr] Compiling borsh v0.9.3 [INFO] [stderr] Compiling ark-ff-macros v0.4.2 [INFO] [stderr] Compiling strum_macros v0.24.3 [INFO] [stderr] Compiling borsh-derive v0.10.4 [INFO] [stderr] Compiling wasm-bindgen-macro v0.2.104 [INFO] [stderr] Compiling near-account-id v0.15.0 [INFO] [stderr] Compiling bv v0.11.1 [INFO] [stderr] Compiling darling_macro v0.20.11 [INFO] [stderr] Compiling darling v0.20.11 [INFO] [stderr] Compiling borsh-derive v1.5.7 [INFO] [stderr] Compiling unicode-normalization v0.1.24 [INFO] [stderr] Compiling hmac-drbg v0.3.0 [INFO] [stderr] Compiling pbkdf2 v0.4.0 [INFO] [stderr] Compiling solana-program v1.18.26 [INFO] [stderr] Compiling serde_bytes v0.11.19 [INFO] [stderr] Compiling atty v0.2.14 [INFO] [stderr] Compiling memmap2 v0.5.10 [INFO] [stderr] Compiling ark-ff v0.4.2 [INFO] [stderr] Compiling memoffset v0.8.0 [INFO] [stderr] Compiling num-rational v0.3.2 [INFO] [stderr] Compiling bytemuck_derive v1.10.1 [INFO] [stderr] Compiling humantime v2.3.0 [INFO] [stderr] Compiling constant_time_eq v0.3.1 [INFO] [stderr] Compiling env_logger v0.9.3 [INFO] [stderr] Compiling chrono v0.4.42 [INFO] [stderr] Compiling sha3 v0.10.8 [INFO] [stderr] Compiling bytemuck v1.23.2 [INFO] [stderr] Compiling tiny-bip39 v0.8.2 [INFO] [stderr] Compiling uint v0.9.5 [INFO] [stderr] Compiling derive_more v0.99.20 [INFO] [stderr] Compiling strum v0.24.1 [INFO] [stderr] Compiling serde_with_macros v2.3.3 [INFO] [stderr] Compiling borsh v0.10.4 [INFO] [stderr] Compiling parking_lot_core v0.9.11 [INFO] [stderr] Compiling num_enum_derive v0.7.4 [INFO] [stderr] Compiling pyo3 v0.18.3 [INFO] [stderr] Compiling hmac v0.12.1 [INFO] [stderr] Compiling pyo3-macros-backend v0.18.3 [INFO] [stderr] Compiling near-rpc-error-core v0.15.0 [INFO] [stderr] Compiling cipher v0.2.5 [INFO] [stderr] Compiling solana-sdk-macro v1.18.26 [INFO] [stderr] Compiling bitflags v2.9.4 [INFO] [stderr] Compiling bincode v1.3.3 [INFO] [stderr] Compiling solana-sdk v1.18.26 [INFO] [stderr] Compiling num-derive v0.4.2 [INFO] [stderr] Compiling derivation-path v0.2.0 [INFO] [stderr] Compiling reed-solomon-erasure v4.0.2 [INFO] [stderr] Compiling qstring v0.7.2 [INFO] [stderr] Compiling ed25519-dalek-bip32 v0.2.0 [INFO] [stderr] Compiling num_enum v0.7.4 [INFO] [stderr] Compiling c2-chacha v0.3.3 [INFO] [stderr] Compiling near-rpc-error-macro v0.15.0 [INFO] [stderr] Compiling serde_with v2.3.3 [INFO] [stderr] Compiling primitive-types v0.10.1 [INFO] [stderr] Compiling parking_lot v0.12.4 [INFO] [stderr] Compiling secp256k1 v0.24.3 [INFO] [stderr] Compiling solana-logger v1.18.26 [INFO] [stderr] Compiling uriparse v0.6.4 [INFO] [stderr] Compiling pbkdf2 v0.11.0 [INFO] [stderr] Compiling blake2 v0.9.2 [INFO] [stderr] Compiling qualifier_attr v0.2.2 [INFO] [stderr] Compiling serde_repr v0.1.20 [INFO] [stderr] Compiling ark-poly v0.4.2 [INFO] [stderr] Compiling unindent v0.1.11 [INFO] [stderr] Compiling indoc v1.0.9 [INFO] [stderr] Compiling assert_matches v1.5.0 [INFO] [stderr] Compiling serde_cbor v0.11.2 [INFO] [stderr] Compiling near-primitives-core v0.15.0 [INFO] [stderr] Compiling ark-ec v0.4.2 [INFO] [stderr] Compiling near-crypto v0.15.0 [INFO] [stderr] Compiling near-vm-errors v0.15.0 [INFO] [stderr] Compiling pyo3-macros v0.18.3 [INFO] [stderr] Compiling smart-default v0.6.0 [INFO] [stderr] Compiling bytesize v1.3.3 [INFO] [stderr] Compiling solders-macros v0.14.4 [INFO] [stderr] Compiling near-primitives v0.15.0 [INFO] [stderr] Compiling ark-bn254 v0.4.0 [INFO] [stderr] Compiling light-poseidon v0.2.0 [INFO] [stderr] Compiling solders-traits v0.14.4 [INFO] [stderr] Compiling pyonear v0.2.0 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/error/exception.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | / create_exception!( [INFO] [stdout] 30 | | pyonear, [INFO] [stdout] 31 | | ParseKeyError, [INFO] [stdout] 32 | | PyException, [INFO] [stdout] 33 | | "Raised when an error is encountered parsing a cryptographic key." [INFO] [stdout] 34 | | ); [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] --> src/error/exception.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | / create_exception!( [INFO] [stdout] 30 | | pyonear, [INFO] [stdout] 31 | | ParseKeyError, [INFO] [stdout] 32 | | PyException, [INFO] [stdout] 33 | | "Raised when an error is encountered parsing a cryptographic key." [INFO] [stdout] 34 | | ); [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] --> src/error/exception.rs:36:1 [INFO] [stdout] | [INFO] [stdout] 36 | / create_exception!( [INFO] [stdout] 37 | | pyonear, [INFO] [stdout] 38 | | ParseSignatureError, [INFO] [stdout] 39 | | PyException, [INFO] [stdout] 40 | | "Raised when an error is encountered parsing a cryptographic signature." [INFO] [stdout] 41 | | ); [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] --> src/error/exception.rs:36:1 [INFO] [stdout] | [INFO] [stdout] 36 | / create_exception!( [INFO] [stdout] 37 | | pyonear, [INFO] [stdout] 38 | | ParseSignatureError, [INFO] [stdout] 39 | | PyException, [INFO] [stdout] 40 | | "Raised when an error is encountered parsing a cryptographic signature." [INFO] [stdout] 41 | | ); [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] --> src/error/exception.rs:43:1 [INFO] [stdout] | [INFO] [stdout] 43 | / create_exception!( [INFO] [stdout] 44 | | pyonear, [INFO] [stdout] 45 | | TryFromSliceError, [INFO] [stdout] 46 | | PyException, [INFO] [stdout] 47 | | "Raised when conversion from a slice to an array fails." [INFO] [stdout] 48 | | ); [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] --> src/error/exception.rs:43:1 [INFO] [stdout] | [INFO] [stdout] 43 | / create_exception!( [INFO] [stdout] 44 | | pyonear, [INFO] [stdout] 45 | | TryFromSliceError, [INFO] [stdout] 46 | | PyException, [INFO] [stdout] 47 | | "Raised when conversion from a slice to an array fails." [INFO] [stdout] 48 | | ); [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] --> src/error/exception.rs:50:1 [INFO] [stdout] | [INFO] [stdout] 50 | / create_exception!( [INFO] [stdout] 51 | | pyonear, [INFO] [stdout] 52 | | Secp256K1Error, [INFO] [stdout] 53 | | PyException, [INFO] [stdout] 54 | | "Raised when an error is encountered in the secp256k1 library." [INFO] [stdout] 55 | | ); [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] --> src/error/exception.rs:50:1 [INFO] [stdout] | [INFO] [stdout] 50 | / create_exception!( [INFO] [stdout] 51 | | pyonear, [INFO] [stdout] 52 | | Secp256K1Error, [INFO] [stdout] 53 | | PyException, [INFO] [stdout] 54 | | "Raised when an error is encountered in the secp256k1 library." [INFO] [stdout] 55 | | ); [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] --> src/error/core.rs:1058:45 [INFO] [stdout] | [INFO] [stdout] 1058 | fn get_invalid_access_key_error_members(py: Python) -> Vec<&PyType> { [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] 1058 | fn get_invalid_access_key_error_members(py: Python<'_>) -> Vec<&PyType> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error/core.rs:1069:45 [INFO] [stdout] | [INFO] [stdout] 1069 | fn get_actions_validation_error_members(py: Python) -> Vec<&PyType> { [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] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 1069 | fn get_actions_validation_error_members(py: Python<'_>) -> Vec<&PyType> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error/core.rs:1085:37 [INFO] [stdout] | [INFO] [stdout] 1085 | fn get_invalid_tx_error_members(py: Python) -> Vec<&PyType> { [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] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 1085 | fn get_invalid_tx_error_members(py: Python<'_>) -> Vec<&PyType> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error/core.rs:1103:50 [INFO] [stdout] | [INFO] [stdout] 1103 | pub(crate) fn get_tx_execution_error_members(py: Python) -> Vec<&PyType> { [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] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 1103 | pub(crate) fn get_tx_execution_error_members(py: Python<'_>) -> Vec<&PyType> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error/vm.rs:595:55 [INFO] [stdout] | [INFO] [stdout] 595 | pub(crate) fn get_function_call_error_ser_members(py: Python) -> Vec<&PyType> { [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] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 595 | pub(crate) fn get_function_call_error_ser_members(py: Python<'_>) -> Vec<&PyType> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 3m 00s [INFO] running `Command { std: "docker" "inspect" "6f73374f0f6200ffd442d6305958c63fc2732586804ba93678fc9084efe1c4ff", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "6f73374f0f6200ffd442d6305958c63fc2732586804ba93678fc9084efe1c4ff", kill_on_drop: false }` [INFO] [stdout] 6f73374f0f6200ffd442d6305958c63fc2732586804ba93678fc9084efe1c4ff [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-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" "+2440211fe03bc45c89b6dc1a3df18382ce91e32b" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] a61a7250373a78ca74b7bdd1942f400c96ad7a9daed8795a72db759eef06663c [INFO] running `Command { std: "docker" "start" "-a" "a61a7250373a78ca74b7bdd1942f400c96ad7a9daed8795a72db759eef06663c", kill_on_drop: false }` [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/error/exception.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | / create_exception!( [INFO] [stdout] 30 | | pyonear, [INFO] [stdout] 31 | | ParseKeyError, [INFO] [stdout] 32 | | PyException, [INFO] [stdout] 33 | | "Raised when an error is encountered parsing a cryptographic key." [INFO] [stdout] 34 | | ); [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] --> src/error/exception.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | / create_exception!( [INFO] [stdout] 30 | | pyonear, [INFO] [stdout] 31 | | ParseKeyError, [INFO] [stdout] 32 | | PyException, [INFO] [stdout] 33 | | "Raised when an error is encountered parsing a cryptographic key." [INFO] [stdout] 34 | | ); [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] --> src/error/exception.rs:36:1 [INFO] [stdout] | [INFO] [stdout] 36 | / create_exception!( [INFO] [stdout] 37 | | pyonear, [INFO] [stdout] 38 | | ParseSignatureError, [INFO] [stdout] 39 | | PyException, [INFO] [stdout] 40 | | "Raised when an error is encountered parsing a cryptographic signature." [INFO] [stdout] 41 | | ); [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] --> src/error/exception.rs:36:1 [INFO] [stdout] | [INFO] [stdout] 36 | / create_exception!( [INFO] [stdout] 37 | | pyonear, [INFO] [stdout] 38 | | ParseSignatureError, [INFO] [stdout] 39 | | PyException, [INFO] [stdout] 40 | | "Raised when an error is encountered parsing a cryptographic signature." [INFO] [stdout] 41 | | ); [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] --> src/error/exception.rs:43:1 [INFO] [stdout] | [INFO] [stdout] 43 | / create_exception!( [INFO] [stdout] 44 | | pyonear, [INFO] [stdout] 45 | | TryFromSliceError, [INFO] [stdout] 46 | | PyException, [INFO] [stdout] 47 | | "Raised when conversion from a slice to an array fails." [INFO] [stdout] 48 | | ); [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] --> src/error/exception.rs:43:1 [INFO] [stdout] | [INFO] [stdout] 43 | / create_exception!( [INFO] [stdout] 44 | | pyonear, [INFO] [stdout] 45 | | TryFromSliceError, [INFO] [stdout] 46 | | PyException, [INFO] [stdout] 47 | | "Raised when conversion from a slice to an array fails." [INFO] [stdout] 48 | | ); [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] --> src/error/exception.rs:50:1 [INFO] [stdout] | [INFO] [stdout] 50 | / create_exception!( [INFO] [stdout] 51 | | pyonear, [INFO] [stdout] 52 | | Secp256K1Error, [INFO] [stdout] 53 | | PyException, [INFO] [stdout] 54 | | "Raised when an error is encountered in the secp256k1 library." [INFO] [stdout] 55 | | ); [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] --> src/error/exception.rs:50:1 [INFO] [stdout] | [INFO] [stdout] 50 | / create_exception!( [INFO] [stdout] 51 | | pyonear, [INFO] [stdout] 52 | | Secp256K1Error, [INFO] [stdout] 53 | | PyException, [INFO] [stdout] 54 | | "Raised when an error is encountered in the secp256k1 library." [INFO] [stdout] 55 | | ); [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] --> src/error/core.rs:1058:45 [INFO] [stdout] | [INFO] [stdout] 1058 | fn get_invalid_access_key_error_members(py: Python) -> Vec<&PyType> { [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] 1058 | fn get_invalid_access_key_error_members(py: Python<'_>) -> Vec<&PyType> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error/core.rs:1069:45 [INFO] [stdout] | [INFO] [stdout] 1069 | fn get_actions_validation_error_members(py: Python) -> Vec<&PyType> { [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] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 1069 | fn get_actions_validation_error_members(py: Python<'_>) -> Vec<&PyType> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error/core.rs:1085:37 [INFO] [stdout] | [INFO] [stdout] 1085 | fn get_invalid_tx_error_members(py: Python) -> Vec<&PyType> { [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] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 1085 | fn get_invalid_tx_error_members(py: Python<'_>) -> Vec<&PyType> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error/core.rs:1103:50 [INFO] [stdout] | [INFO] [stdout] 1103 | pub(crate) fn get_tx_execution_error_members(py: Python) -> Vec<&PyType> { [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] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 1103 | pub(crate) fn get_tx_execution_error_members(py: Python<'_>) -> Vec<&PyType> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error/vm.rs:595:55 [INFO] [stdout] | [INFO] [stdout] 595 | pub(crate) fn get_function_call_error_ser_members(py: Python) -> Vec<&PyType> { [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] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 595 | pub(crate) fn get_function_call_error_ser_members(py: Python<'_>) -> Vec<&PyType> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling pyonear v0.2.0 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/error/exception.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | / create_exception!( [INFO] [stdout] 30 | | pyonear, [INFO] [stdout] 31 | | ParseKeyError, [INFO] [stdout] 32 | | PyException, [INFO] [stdout] 33 | | "Raised when an error is encountered parsing a cryptographic key." [INFO] [stdout] 34 | | ); [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] --> src/error/exception.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | / create_exception!( [INFO] [stdout] 30 | | pyonear, [INFO] [stdout] 31 | | ParseKeyError, [INFO] [stdout] 32 | | PyException, [INFO] [stdout] 33 | | "Raised when an error is encountered parsing a cryptographic key." [INFO] [stdout] 34 | | ); [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] --> src/error/exception.rs:36:1 [INFO] [stdout] | [INFO] [stdout] 36 | / create_exception!( [INFO] [stdout] 37 | | pyonear, [INFO] [stdout] 38 | | ParseSignatureError, [INFO] [stdout] 39 | | PyException, [INFO] [stdout] 40 | | "Raised when an error is encountered parsing a cryptographic signature." [INFO] [stdout] 41 | | ); [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] --> src/error/exception.rs:36:1 [INFO] [stdout] | [INFO] [stdout] 36 | / create_exception!( [INFO] [stdout] 37 | | pyonear, [INFO] [stdout] 38 | | ParseSignatureError, [INFO] [stdout] 39 | | PyException, [INFO] [stdout] 40 | | "Raised when an error is encountered parsing a cryptographic signature." [INFO] [stdout] 41 | | ); [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] --> src/error/exception.rs:43:1 [INFO] [stdout] | [INFO] [stdout] 43 | / create_exception!( [INFO] [stdout] 44 | | pyonear, [INFO] [stdout] 45 | | TryFromSliceError, [INFO] [stdout] 46 | | PyException, [INFO] [stdout] 47 | | "Raised when conversion from a slice to an array fails." [INFO] [stdout] 48 | | ); [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] --> src/error/exception.rs:43:1 [INFO] [stdout] | [INFO] [stdout] 43 | / create_exception!( [INFO] [stdout] 44 | | pyonear, [INFO] [stdout] 45 | | TryFromSliceError, [INFO] [stdout] 46 | | PyException, [INFO] [stdout] 47 | | "Raised when conversion from a slice to an array fails." [INFO] [stdout] 48 | | ); [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] --> src/error/exception.rs:50:1 [INFO] [stdout] | [INFO] [stdout] 50 | / create_exception!( [INFO] [stdout] 51 | | pyonear, [INFO] [stdout] 52 | | Secp256K1Error, [INFO] [stdout] 53 | | PyException, [INFO] [stdout] 54 | | "Raised when an error is encountered in the secp256k1 library." [INFO] [stdout] 55 | | ); [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] --> src/error/exception.rs:50:1 [INFO] [stdout] | [INFO] [stdout] 50 | / create_exception!( [INFO] [stdout] 51 | | pyonear, [INFO] [stdout] 52 | | Secp256K1Error, [INFO] [stdout] 53 | | PyException, [INFO] [stdout] 54 | | "Raised when an error is encountered in the secp256k1 library." [INFO] [stdout] 55 | | ); [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] --> src/error/core.rs:1058:45 [INFO] [stdout] | [INFO] [stdout] 1058 | fn get_invalid_access_key_error_members(py: Python) -> Vec<&PyType> { [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] 1058 | fn get_invalid_access_key_error_members(py: Python<'_>) -> Vec<&PyType> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error/core.rs:1069:45 [INFO] [stdout] | [INFO] [stdout] 1069 | fn get_actions_validation_error_members(py: Python) -> Vec<&PyType> { [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] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 1069 | fn get_actions_validation_error_members(py: Python<'_>) -> Vec<&PyType> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error/core.rs:1085:37 [INFO] [stdout] | [INFO] [stdout] 1085 | fn get_invalid_tx_error_members(py: Python) -> Vec<&PyType> { [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] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 1085 | fn get_invalid_tx_error_members(py: Python<'_>) -> Vec<&PyType> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error/core.rs:1103:50 [INFO] [stdout] | [INFO] [stdout] 1103 | pub(crate) fn get_tx_execution_error_members(py: Python) -> Vec<&PyType> { [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] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 1103 | pub(crate) fn get_tx_execution_error_members(py: Python<'_>) -> Vec<&PyType> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/error/vm.rs:595:55 [INFO] [stdout] | [INFO] [stdout] 595 | pub(crate) fn get_function_call_error_ser_members(py: Python) -> Vec<&PyType> { [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] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 595 | pub(crate) fn get_function_call_error_ser_members(py: Python<'_>) -> Vec<&PyType> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 22.84s [INFO] running `Command { std: "docker" "inspect" "a61a7250373a78ca74b7bdd1942f400c96ad7a9daed8795a72db759eef06663c", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "a61a7250373a78ca74b7bdd1942f400c96ad7a9daed8795a72db759eef06663c", kill_on_drop: false }` [INFO] [stdout] a61a7250373a78ca74b7bdd1942f400c96ad7a9daed8795a72db759eef06663c [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-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" "+2440211fe03bc45c89b6dc1a3df18382ce91e32b" "test" "--frozen", kill_on_drop: false }` [INFO] [stdout] f4f86ca7d1e8ce9dd513a5f0816d8a7b17c8979e32b61887b9b8a9d21566c70c [INFO] running `Command { std: "docker" "start" "-a" "f4f86ca7d1e8ce9dd513a5f0816d8a7b17c8979e32b61887b9b8a9d21566c70c", kill_on_drop: false }` [INFO] [stderr] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stderr] --> src/error/exception.rs:29:1 [INFO] [stderr] | [INFO] [stderr] 29 | / create_exception!( [INFO] [stderr] 30 | | pyonear, [INFO] [stderr] 31 | | ParseKeyError, [INFO] [stderr] 32 | | PyException, [INFO] [stderr] 33 | | "Raised when an error is encountered parsing a cryptographic key." [INFO] [stderr] 34 | | ); [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] --> src/error/exception.rs:29:1 [INFO] [stderr] | [INFO] [stderr] 29 | / create_exception!( [INFO] [stderr] 30 | | pyonear, [INFO] [stderr] 31 | | ParseKeyError, [INFO] [stderr] 32 | | PyException, [INFO] [stderr] 33 | | "Raised when an error is encountered parsing a cryptographic key." [INFO] [stderr] 34 | | ); [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] --> src/error/exception.rs:36:1 [INFO] [stderr] | [INFO] [stderr] 36 | / create_exception!( [INFO] [stderr] 37 | | pyonear, [INFO] [stderr] 38 | | ParseSignatureError, [INFO] [stderr] 39 | | PyException, [INFO] [stderr] 40 | | "Raised when an error is encountered parsing a cryptographic signature." [INFO] [stderr] 41 | | ); [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] --> src/error/exception.rs:43:1 [INFO] [stderr] | [INFO] [stderr] 43 | / create_exception!( [INFO] [stderr] 44 | | pyonear, [INFO] [stderr] 45 | | TryFromSliceError, [INFO] [stderr] 46 | | PyException, [INFO] [stderr] 47 | | "Raised when conversion from a slice to an array fails." [INFO] [stderr] 48 | | ); [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] --> src/error/exception.rs:50:1 [INFO] [stderr] | [INFO] [stderr] 50 | / create_exception!( [INFO] [stderr] 51 | | pyonear, [INFO] [stderr] 52 | | Secp256K1Error, [INFO] [stderr] 53 | | PyException, [INFO] [stderr] 54 | | "Raised when an error is encountered in the secp256k1 library." [INFO] [stderr] 55 | | ); [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] --> src/error/core.rs:1058:45 [INFO] [stderr] | [INFO] [stderr] 1058 | fn get_invalid_access_key_error_members(py: Python) -> Vec<&PyType> { [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] 1058 | fn get_invalid_access_key_error_members(py: Python<'_>) -> Vec<&PyType> { [INFO] [stderr] | ++++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/error/core.rs:1069:45 [INFO] [stderr] | [INFO] [stderr] 1069 | fn get_actions_validation_error_members(py: Python) -> Vec<&PyType> { [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] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 1069 | fn get_actions_validation_error_members(py: Python<'_>) -> Vec<&PyType> { [INFO] [stderr] | ++++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/error/core.rs:1085:37 [INFO] [stderr] | [INFO] [stderr] 1085 | fn get_invalid_tx_error_members(py: Python) -> Vec<&PyType> { [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] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 1085 | fn get_invalid_tx_error_members(py: Python<'_>) -> Vec<&PyType> { [INFO] [stderr] | ++++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/error/core.rs:1103:50 [INFO] [stderr] | [INFO] [stderr] 1103 | pub(crate) fn get_tx_execution_error_members(py: Python) -> Vec<&PyType> { [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] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 1103 | pub(crate) fn get_tx_execution_error_members(py: Python<'_>) -> Vec<&PyType> { [INFO] [stderr] | ++++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/error/vm.rs:595:55 [INFO] [stderr] | [INFO] [stderr] 595 | pub(crate) fn get_function_call_error_ser_members(py: Python) -> Vec<&PyType> { [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] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 595 | pub(crate) fn get_function_call_error_ser_members(py: Python<'_>) -> Vec<&PyType> { [INFO] [stderr] | ++++ [INFO] [stderr] [INFO] [stderr] warning: `pyonear` (lib) generated 13 warnings (3 duplicates) (run `cargo fix --lib -p pyonear` to apply 5 suggestions) [INFO] [stderr] warning: `pyonear` (lib test) generated 13 warnings (13 duplicates) [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 0.43s [INFO] [stderr] Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/pyonear-213187e9828f124e) [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] Doc-tests pyonear [INFO] [stdout] [INFO] [stdout] running 8 tests [INFO] [stdout] test src/account_id.rs - account_id::AccountId::is_top_level (line 79) ... FAILED [INFO] [stdout] test src/account_id.rs - account_id::AccountId::is_system (line 137) ... FAILED [INFO] [stdout] test src/account_id.rs - account_id::AccountId::is_implicit (line 120) ... FAILED [INFO] [stdout] test src/account_id.rs - account_id::AccountId::is_sub_account_of (line 97) ... FAILED [INFO] [stdout] test src/crypto_hash.rs - crypto_hash::crypto_hash (line 108) ... FAILED [INFO] [stdout] test src/account_id.rs - account_id::AccountId::validate (line 153) ... FAILED [INFO] [stdout] test src/account_id.rs - account_id::AccountId (line 23) ... FAILED [INFO] [stdout] test src/transaction.rs - transaction::Transaction (line 62) ... FAILED [INFO] [stdout] [INFO] [stdout] failures: [INFO] [stdout] [INFO] [stdout] ---- src/account_id.rs - account_id::AccountId::is_top_level (line 79) stdout ---- [INFO] [stdout] error: expected item, found `>>` [INFO] [stdout] --> src/account_id.rs:80:1 [INFO] [stdout] | [INFO] [stdout] 1 | >>> from pyonear.account_id import AccountId [INFO] [stdout] | ^^ expected item [INFO] [stdout] | [INFO] [stdout] = note: for a full list of items that can appear in modules, see [INFO] [stdout] [INFO] [stdout] error: aborting due to 1 previous error [INFO] [stdout] [INFO] [stdout] Couldn't compile the test. [INFO] [stdout] ---- src/account_id.rs - account_id::AccountId::is_system (line 137) stdout ---- [INFO] [stdout] error: expected item, found `>>` [INFO] [stdout] --> src/account_id.rs:138:1 [INFO] [stdout] | [INFO] [stdout] 1 | >>> from pyonear.account_id import AccountId [INFO] [stdout] | ^^ expected item [INFO] [stdout] | [INFO] [stdout] = note: for a full list of items that can appear in modules, see [INFO] [stdout] [INFO] [stdout] error: aborting due to 1 previous error [INFO] [stdout] [INFO] [stdout] Couldn't compile the test. [INFO] [stdout] ---- src/account_id.rs - account_id::AccountId::is_implicit (line 120) stdout ---- [INFO] [stdout] error: expected item, found `>>` [INFO] [stdout] --> src/account_id.rs:121:1 [INFO] [stdout] | [INFO] [stdout] 1 | >>> from pyonear.account_id import AccountId [INFO] [stdout] | ^^ expected item [INFO] [stdout] | [INFO] [stdout] = note: for a full list of items that can appear in modules, see [INFO] [stdout] [INFO] [stdout] error: aborting due to 1 previous error [INFO] [stdout] [INFO] [stdout] Couldn't compile the test. [INFO] [stdout] ---- src/account_id.rs - account_id::AccountId::is_sub_account_of (line 97) stdout ---- [INFO] [stdout] error: expected item, found `>>` [INFO] [stdout] --> src/account_id.rs:98:1 [INFO] [stdout] | [INFO] [stdout] 1 | >>> from pyonear.account_id import AccountId [INFO] [stdout] | ^^ expected item [INFO] [stdout] | [INFO] [stdout] = note: for a full list of items that can appear in modules, see [INFO] [stdout] [INFO] [stdout] error: aborting due to 1 previous error [INFO] [stdout] [INFO] [stdout] Couldn't compile the test. [INFO] [stdout] ---- src/crypto_hash.rs - crypto_hash::crypto_hash (line 108) stdout ---- [INFO] [stdout] error: unknown start of token: ` [INFO] [stdout] --> src/crypto_hash.rs:112:5 [INFO] [stdout] | [INFO] [stdout] 4 | `EutHBsdT1YCzHxjCfQHnLPL1vFrkSyLSio4vkphfnEk`, [INFO] [stdout] | ^ [INFO] [stdout] | [INFO] [stdout] help: Unicode character '`' (Grave Accent) looks like ''' (Single Quote), but it is not [INFO] [stdout] | [INFO] [stdout] 4 - `EutHBsdT1YCzHxjCfQHnLPL1vFrkSyLSio4vkphfnEk`, [INFO] [stdout] 4 + 'EutHBsdT1YCzHxjCfQHnLPL1vFrkSyLSio4vkphfnEk`, [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] error: unknown start of token: ` [INFO] [stdout] --> src/crypto_hash.rs:112:49 [INFO] [stdout] | [INFO] [stdout] 4 | `EutHBsdT1YCzHxjCfQHnLPL1vFrkSyLSio4vkphfnEk`, [INFO] [stdout] | ^ [INFO] [stdout] | [INFO] [stdout] help: Unicode character '`' (Grave Accent) looks like ''' (Single Quote), but it is not [INFO] [stdout] | [INFO] [stdout] 4 - `EutHBsdT1YCzHxjCfQHnLPL1vFrkSyLSio4vkphfnEk`, [INFO] [stdout] 4 + `EutHBsdT1YCzHxjCfQHnLPL1vFrkSyLSio4vkphfnEk', [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] error: expected item, found `>>` [INFO] [stdout] --> src/crypto_hash.rs:109:1 [INFO] [stdout] | [INFO] [stdout] 1 | >>> from pyonear.crypto_hash import crypto_hash [INFO] [stdout] | ^^ expected item [INFO] [stdout] | [INFO] [stdout] = note: for a full list of items that can appear in modules, see [INFO] [stdout] [INFO] [stdout] error: aborting due to 3 previous errors [INFO] [stdout] [INFO] [stdout] Couldn't compile the test. [INFO] [stdout] ---- src/account_id.rs - account_id::AccountId::validate (line 153) stdout ---- [INFO] [stdout] error: expected item, found `>>` [INFO] [stdout] --> src/account_id.rs:154:1 [INFO] [stdout] | [INFO] [stdout] 1 | >>> from pyonear.account_id import AccountId [INFO] [stdout] | ^^ expected item [INFO] [stdout] | [INFO] [stdout] = note: for a full list of items that can appear in modules, see [INFO] [stdout] [INFO] [stdout] error: aborting due to 1 previous error [INFO] [stdout] [INFO] [stdout] Couldn't compile the test. [INFO] [stdout] ---- src/account_id.rs - account_id::AccountId (line 23) stdout ---- [INFO] [stdout] error: expected item, found `>>` [INFO] [stdout] --> src/account_id.rs:24:1 [INFO] [stdout] | [INFO] [stdout] 1 | >>> from pyonear.account_id import AccountId [INFO] [stdout] | ^^ expected item [INFO] [stdout] | [INFO] [stdout] = note: for a full list of items that can appear in modules, see [INFO] [stdout] [INFO] [stdout] error: aborting due to 1 previous error [INFO] [stdout] [INFO] [stdout] Couldn't compile the test. [INFO] [stdout] ---- src/transaction.rs - transaction::Transaction (line 62) stdout ---- [INFO] [stdout] error: unknown start of token: ` [INFO] [stdout] --> src/transaction.rs:65:101 [INFO] [stdout] | [INFO] [stdout] 3 | nonce (int): Used to determine order of transaction in the pool. It increments for a combination of `signer_id` and `public_key`, [INFO] [stdout] | ^ [INFO] [stdout] | [INFO] [stdout] help: Unicode character '`' (Grave Accent) looks like ''' (Single Quote), but it is not [INFO] [stdout] | [INFO] [stdout] 3 - nonce (int): Used to determine order of transaction in the pool. It increments for a combination of `signer_id` and `public_key`, [INFO] [stdout] 3 + nonce (int): Used to determine order of transaction in the pool. It increments for a combination of 'signer_id` and `public_key`, [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] error: unknown start of token: ` [INFO] [stdout] --> src/transaction.rs:65:111 [INFO] [stdout] | [INFO] [stdout] 3 | nonce (int): Used to determine order of transaction in the pool. It increments for a combination of `signer_id` and `public_key`, [INFO] [stdout] | ^ [INFO] [stdout] | [INFO] [stdout] help: Unicode character '`' (Grave Accent) looks like ''' (Single Quote), but it is not [INFO] [stdout] | [INFO] [stdout] 3 - nonce (int): Used to determine order of transaction in the pool. It increments for a combination of `signer_id` and `public_key`, [INFO] [stdout] 3 + nonce (int): Used to determine order of transaction in the pool. It increments for a combination of `signer_id' and `public_key`, [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] error: unknown start of token: ` [INFO] [stdout] --> src/transaction.rs:65:117 [INFO] [stdout] | [INFO] [stdout] 3 | nonce (int): Used to determine order of transaction in the pool. It increments for a combination of `signer_id` and `public_key`, [INFO] [stdout] | ^ [INFO] [stdout] | [INFO] [stdout] help: Unicode character '`' (Grave Accent) looks like ''' (Single Quote), but it is not [INFO] [stdout] | [INFO] [stdout] 3 - nonce (int): Used to determine order of transaction in the pool. It increments for a combination of `signer_id` and `public_key`, [INFO] [stdout] 3 + nonce (int): Used to determine order of transaction in the pool. It increments for a combination of `signer_id` and 'public_key`, [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] error: unknown start of token: ` [INFO] [stdout] --> src/transaction.rs:65:128 [INFO] [stdout] | [INFO] [stdout] 3 | nonce (int): Used to determine order of transaction in the pool. It increments for a combination of `signer_id` and `public_key`, [INFO] [stdout] | ^ [INFO] [stdout] | [INFO] [stdout] help: Unicode character '`' (Grave Accent) looks like ''' (Single Quote), but it is not [INFO] [stdout] | [INFO] [stdout] 3 - nonce (int): Used to determine order of transaction in the pool. It increments for a combination of `signer_id` and `public_key`, [INFO] [stdout] 3 + nonce (int): Used to determine order of transaction in the pool. It increments for a combination of `signer_id` and `public_key', [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] error: missing `fn` or `struct` for function or struct definition [INFO] [stdout] --> src/transaction.rs:63:1 [INFO] [stdout] | [INFO] [stdout] 1 | signer_id (AccountId): The account on whose behalf the transaciton is signed. [INFO] [stdout] | ^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] help: if you meant to call a macro, try [INFO] [stdout] | [INFO] [stdout] 1 | signer_id! (AccountId): The account on whose behalf the transaciton is signed. [INFO] [stdout] | + [INFO] [stdout] [INFO] [stdout] error: aborting due to 5 previous errors [INFO] [stdout] [INFO] [stdout] Couldn't compile the test. [INFO] [stdout] [INFO] [stdout] failures: [INFO] [stdout] src/account_id.rs - account_id::AccountId (line 23) [INFO] [stdout] src/account_id.rs - account_id::AccountId::is_implicit (line 120) [INFO] [stdout] src/account_id.rs - account_id::AccountId::is_sub_account_of (line 97) [INFO] [stdout] src/account_id.rs - account_id::AccountId::is_system (line 137) [INFO] [stdout] src/account_id.rs - account_id::AccountId::is_top_level (line 79) [INFO] [stdout] src/account_id.rs - account_id::AccountId::validate (line 153) [INFO] [stdout] src/crypto_hash.rs - crypto_hash::crypto_hash (line 108) [INFO] [stdout] src/transaction.rs - transaction::Transaction (line 62) [INFO] [stdout] [INFO] [stdout] test result: FAILED. 0 passed; 8 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.22s [INFO] [stdout] [INFO] [stderr] error: doctest failed, to rerun pass `--doc` [INFO] running `Command { std: "docker" "inspect" "f4f86ca7d1e8ce9dd513a5f0816d8a7b17c8979e32b61887b9b8a9d21566c70c", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "f4f86ca7d1e8ce9dd513a5f0816d8a7b17c8979e32b61887b9b8a9d21566c70c", kill_on_drop: false }` [INFO] [stdout] f4f86ca7d1e8ce9dd513a5f0816d8a7b17c8979e32b61887b9b8a9d21566c70c