[INFO] fetching crate ggca 1.0.0... [INFO] testing ggca-1.0.0 against 1.90.0 for beta-1.91-3 [INFO] extracting crate ggca 1.0.0 into /workspace/builds/worker-5-tc1/source [INFO] started tweaking crates.io crate ggca 1.0.0 [INFO] removed 0 missing examples [INFO] removed 0 missing tests [INFO] finished tweaking crates.io crate ggca 1.0.0 [INFO] tweaked toml for crates.io crate ggca 1.0.0 written to /workspace/builds/worker-5-tc1/source/Cargo.toml [INFO] validating manifest of crates.io crate ggca 1.0.0 on toolchain 1.90.0 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+1.90.0" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate crates.io crate ggca 1.0.0 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" "+1.90.0" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating crates.io index [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded nalgebra-macros v0.2.2 [INFO] [stderr] Downloaded unindent v0.2.3 [INFO] [stderr] Downloaded is-terminal v0.4.12 [INFO] [stderr] Downloaded plotters-svg v0.3.6 [INFO] [stderr] Downloaded anstyle v1.0.7 [INFO] [stderr] Downloaded clap_lex v0.7.1 [INFO] [stderr] Downloaded plotters-backend v0.3.6 [INFO] [stderr] Downloaded camino v1.1.7 [INFO] [stderr] Downloaded clap v4.5.9 [INFO] [stderr] Downloaded fast-float v0.2.0 [INFO] [stderr] Downloaded safe_arch v0.7.2 [INFO] [stderr] Downloaded wide v0.7.25 [INFO] [stderr] Downloaded statrs v0.17.1 [INFO] [stderr] Downloaded clap_builder v4.5.9 [INFO] [stderr] Downloaded portable-atomic v1.6.0 [INFO] [stderr] Downloaded plotters v0.3.6 [INFO] [stderr] Downloaded pyo3-ffi v0.22.2 [INFO] [stderr] Downloaded pyo3-macros-backend v0.22.2 [INFO] [stderr] Downloaded matrixmultiply v0.3.8 [INFO] [stderr] Downloaded extsort v0.4.2 [INFO] [stderr] Downloaded target-lexicon v0.12.15 [INFO] [stderr] Downloaded pyo3-build-config v0.22.2 [INFO] [stderr] Downloaded cargo-platform v0.1.8 [INFO] [stderr] Downloaded indoc v2.0.5 [INFO] [stderr] Downloaded pyo3-macros v0.22.2 [INFO] [stderr] Downloaded pyo3 v0.22.2 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+1.90.0" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] fe38ee015adbf06a492a4b1a51324dafcd71412cd18fbcc60db0e9dd9b362569 [INFO] running `Command { std: "docker" "start" "-a" "fe38ee015adbf06a492a4b1a51324dafcd71412cd18fbcc60db0e9dd9b362569", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "fe38ee015adbf06a492a4b1a51324dafcd71412cd18fbcc60db0e9dd9b362569", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "fe38ee015adbf06a492a4b1a51324dafcd71412cd18fbcc60db0e9dd9b362569", kill_on_drop: false }` [INFO] [stdout] fe38ee015adbf06a492a4b1a51324dafcd71412cd18fbcc60db0e9dd9b362569 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-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" "+1.90.0" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 06b588efbf5d6e7adb9bee9514fa4ef32969b0a1044e8e00fdba944a987fa92e [INFO] running `Command { std: "docker" "start" "-a" "06b588efbf5d6e7adb9bee9514fa4ef32969b0a1044e8e00fdba944a987fa92e", kill_on_drop: false }` [INFO] [stderr] Compiling quote v1.0.36 [INFO] [stderr] Compiling autocfg v1.3.0 [INFO] [stderr] Compiling target-lexicon v0.12.15 [INFO] [stderr] Compiling libc v0.2.155 [INFO] [stderr] Compiling serde v1.0.204 [INFO] [stderr] Compiling libm v0.2.8 [INFO] [stderr] Compiling camino v1.1.7 [INFO] [stderr] Compiling crossbeam-utils v0.8.20 [INFO] [stderr] Compiling rustix v0.38.34 [INFO] [stderr] Compiling serde_json v1.0.120 [INFO] [stderr] Compiling unicase v2.7.0 [INFO] [stderr] Compiling bitflags v2.6.0 [INFO] [stderr] Compiling semver v1.0.23 [INFO] [stderr] Compiling error-chain v0.12.4 [INFO] [stderr] Compiling linux-raw-sys v0.4.14 [INFO] [stderr] Compiling pulldown-cmark v0.9.6 [INFO] [stderr] Compiling syn v2.0.70 [INFO] [stderr] Compiling bytemuck v1.16.1 [INFO] [stderr] Compiling ppv-lite86 v0.2.17 [INFO] [stderr] Compiling fastrand v2.1.0 [INFO] [stderr] Compiling same-file v1.0.6 [INFO] [stderr] Compiling glob v0.3.1 [INFO] [stderr] Compiling walkdir v2.5.0 [INFO] [stderr] Compiling bytecount v0.6.8 [INFO] [stderr] Compiling aho-corasick v1.1.3 [INFO] [stderr] Compiling safe_arch v0.7.2 [INFO] [stderr] Compiling num-traits v0.2.19 [INFO] [stderr] Compiling matrixmultiply v0.3.8 [INFO] [stderr] Compiling memoffset v0.9.1 [INFO] [stderr] Compiling regex-syntax v0.8.4 [INFO] [stderr] Compiling either v1.13.0 [INFO] [stderr] Compiling wide v0.7.25 [INFO] [stderr] Compiling rawpointer v0.2.1 [INFO] [stderr] Compiling pyo3-build-config v0.22.2 [INFO] [stderr] Compiling csv-core v0.1.11 [INFO] [stderr] Compiling unindent v0.2.3 [INFO] [stderr] Compiling indoc v2.0.5 [INFO] [stderr] Compiling termcolor v1.4.1 [INFO] [stderr] Compiling crossbeam-epoch v0.9.18 [INFO] [stderr] Compiling log v0.4.22 [INFO] [stderr] Compiling humantime v2.1.0 [INFO] [stderr] Compiling crossbeam-deque v0.8.5 [INFO] [stderr] Compiling itertools v0.9.0 [INFO] [stderr] Compiling fast-float v0.2.0 [INFO] [stderr] Compiling rayon-core v1.12.1 [INFO] [stderr] Compiling getrandom v0.2.15 [INFO] [stderr] Compiling rayon v1.10.0 [INFO] [stderr] Compiling atty v0.2.14 [INFO] [stderr] Compiling rand_core v0.6.4 [INFO] [stderr] Compiling rand_chacha v0.3.1 [INFO] [stderr] Compiling num-integer v0.1.46 [INFO] [stderr] Compiling num-complex v0.4.6 [INFO] [stderr] Compiling approx v0.5.1 [INFO] [stderr] Compiling rand v0.8.5 [INFO] [stderr] Compiling pyo3-macros-backend v0.22.2 [INFO] [stderr] Compiling pyo3-ffi v0.22.2 [INFO] [stderr] Compiling pyo3 v0.22.2 [INFO] [stderr] Compiling num-rational v0.4.2 [INFO] [stderr] Compiling simba v0.8.1 [INFO] [stderr] Compiling tempfile v3.10.1 [INFO] [stderr] Compiling regex-automata v0.4.7 [INFO] [stderr] Compiling rand_distr v0.4.3 [INFO] [stderr] Compiling serde_derive v1.0.204 [INFO] [stderr] Compiling nalgebra-macros v0.2.2 [INFO] [stderr] Compiling regex v1.10.5 [INFO] [stderr] Compiling env_logger v0.9.3 [INFO] [stderr] Compiling nalgebra v0.32.6 [INFO] [stderr] Compiling pyo3-macros v0.22.2 [INFO] [stderr] Compiling cargo-platform v0.1.8 [INFO] [stderr] Compiling csv v1.3.0 [INFO] [stderr] Compiling bincode v1.3.3 [INFO] [stderr] Compiling cargo_metadata v0.14.2 [INFO] [stderr] Compiling skeptic v0.13.7 [INFO] [stderr] Compiling extsort v0.4.2 [INFO] [stderr] Compiling statrs v0.17.1 [INFO] [stderr] Compiling ggca v1.0.0 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 38.70s [INFO] running `Command { std: "docker" "inspect" "06b588efbf5d6e7adb9bee9514fa4ef32969b0a1044e8e00fdba944a987fa92e", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "06b588efbf5d6e7adb9bee9514fa4ef32969b0a1044e8e00fdba944a987fa92e", kill_on_drop: false }` [INFO] [stdout] 06b588efbf5d6e7adb9bee9514fa4ef32969b0a1044e8e00fdba944a987fa92e [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-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" "+1.90.0" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 2447d7bc4450c7dc23079f0418efb380198191049128c3b0495891bb7b55854e [INFO] running `Command { std: "docker" "start" "-a" "2447d7bc4450c7dc23079f0418efb380198191049128c3b0495891bb7b55854e", kill_on_drop: false }` [INFO] [stderr] Compiling serde_json v1.0.120 [INFO] [stderr] Compiling half v2.4.1 [INFO] [stderr] Compiling clap_lex v0.7.1 [INFO] [stderr] Compiling anstyle v1.0.7 [INFO] [stderr] Compiling ciborium-io v0.2.2 [INFO] [stderr] Compiling plotters-backend v0.3.6 [INFO] [stderr] Compiling itertools v0.10.5 [INFO] [stderr] Compiling cast v0.3.0 [INFO] [stderr] Compiling is-terminal v0.4.12 [INFO] [stderr] Compiling anes v0.1.6 [INFO] [stderr] Compiling oorandom v11.1.4 [INFO] [stderr] Compiling plotters-svg v0.3.6 [INFO] [stderr] Compiling ciborium-ll v0.2.2 [INFO] [stderr] Compiling plotters v0.3.6 [INFO] [stderr] Compiling clap_builder v4.5.9 [INFO] [stderr] Compiling ciborium v0.2.2 [INFO] [stderr] Compiling cargo_metadata v0.14.2 [INFO] [stderr] Compiling tinytemplate v1.2.1 [INFO] [stderr] Compiling criterion-plot v0.5.0 [INFO] [stderr] Compiling skeptic v0.13.7 [INFO] [stderr] Compiling clap v4.5.9 [INFO] [stderr] Compiling criterion v0.5.1 [INFO] [stderr] Compiling extsort v0.4.2 [INFO] [stderr] Compiling ggca v1.0.0 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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] error: linking with `cc` failed: exit status: 1 [INFO] [stdout] | [INFO] [stdout] = note: "cc" "-m64" "/tmp/rustcVLAwT9/symbols.o" "<2 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "/opt/rustwide/target/debug/deps/{libggca,libfast_float-f50e7f03fe3e35fc,libenv_logger-c14fd8c91b7fc71d,libatty-da15ccfbad80956e,libtermcolor-8f179e788fdc4b43,libhumantime-05b80b6cd1fafc41,libregex-55e0398aed73f152,libregex_automata-4662c386771adf4f,libaho_corasick-c3edd29732527541,libregex_syntax-6eae2ba83f4da8ae,libcsv-c2c155792aa9ec5e,libryu-ab986272b407cd41,libitoa-dceb2e2ec68b27be,libcsv_core-794db0f3d3a9fe9e,libmemchr-8483526b530fc45f,libstatrs-24037c687c986fc9,libnalgebra-ba8d522600c39321,librand_distr-ba18101014ecac97,libmatrixmultiply-78bdd29071b808a2,librawpointer-f73a58cd128df828,libnum_rational-527bb4af2a8273af,libnum_integer-eaf56f037f44b96c,libtypenum-edec2471d71e3ff6,libsimba-34e173d5bf61ed5c,libwide-fca37db65854cccb,libsafe_arch-1f8c55e704099ca9,libbytemuck-d64d7e9744cd12ae,libnum_complex-2158d2ce6fbab3b8,librand-7a4aa9d1fdcac6b4,librand_chacha-6a9818b75bb1279b,libppv_lite86-9f3414099d5801d8,librand_core-3554dbca1744bf65,libgetrandom-b51fc064ca144789,libapprox-9ca7c1181f1a7a2b,libnum_traits-cfc634d4f0a04bcf,libbincode-f7697e5c8a3725db,libserde-7d338d6d62bbd6c1,liblog-17d4c04744091b72,libitertools-1910558703caedba,libpyo3-70fc57b7bf2c34f6,libmemoffset-a5a240ae285dd09a,libonce_cell-18f4b407e28e12b6,libpyo3_ffi-e49b8b2c50bfd98a,liblibc-f5c905995cce61d3,libunindent-a660ddbcf1396680,libextsort-d4e00f56949d17fa,libtempfile-33b3cc82cd8a8f5f,libfastrand-8176d9923c123d38,librustix-c831f801e7d2a5d8,libbitflags-e2ae9f1de5f0445f,liblinux_raw_sys-56cc622a5bb02e92,libcfg_if-3183e62f61f23a61,librayon-937ea05ec8e0296c,librayon_core-621f7bd31e10fa17,libcrossbeam_deque-f2c3fd5e7bbfd927,libcrossbeam_epoch-ed4a2d3daceac61a,libcrossbeam_utils-70904e6a5a5294cc,libeither-e3ab338dd559fca0}.rlib" "/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libstd-*,libpanic_unwind-*,libobject-*,libmemchr-*,libaddr2line-*,libgimli-*,librustc_demangle-*,libstd_detect-*,libhashbrown-*,librustc_std_workspace_alloc-*,libminiz_oxide-*,libadler2-*,libunwind-*,libcfg_if-*,liblibc-*,librustc_std_workspace_core-*,liballoc-*,libcore-*,libcompiler_builtins-*}.rlib" "-Wl,-Bdynamic" "-lgcc_s" "-lutil" "-lrt" "-lpthread" "-lm" "-ldl" "-lc" "-L" "/tmp/rustcVLAwT9/raw-dylibs" "-B/lib/rustlib/x86_64-unknown-linux-gnu/bin/gcc-ld" "-fuse-ld=lld" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/opt/rustwide/target/debug/examples/basic-7709f6b0a7677d73" "-Wl,--gc-sections" "-pie" "-Wl,-z,relro,-z,now" "-nodefaultlibs" [INFO] [stdout] = note: some arguments are omitted. use `--verbose` to show all linker arguments [INFO] [stdout] = note: rust-lld: error: undefined symbol: PyExc_Exception [INFO] [stdout] >>> referenced by exceptions.rs:309 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-0.22.2/src/exceptions.rs:309) [INFO] [stdout] >>> ggca.ggca.175a4e69c89838ca-cgu.14.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::had7df04b87b7cbfd) in archive /opt/rustwide/target/debug/deps/libggca.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-0.22.2/src/exceptions.rs:309) [INFO] [stdout] >>> ggca.ggca.175a4e69c89838ca-cgu.14.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::had7df04b87b7cbfd) in archive /opt/rustwide/target/debug/deps/libggca.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: _Py_Dealloc [INFO] [stdout] >>> referenced by object.rs:611 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-ffi-0.22.2/src/object.rs:611) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h2f26f0aed5f89c8f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by object.rs:611 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-ffi-0.22.2/src/object.rs:611) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h88b27dc260f2fdea) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by object.rs:611 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-ffi-0.22.2/src/object.rs:611) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::hc2ba13d66f24e9d9) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced 4 more times [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyObject_Repr [INFO] [stdout] >>> referenced by any.rs:2277 (src/types/any.rs:2277) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::repr::h865265723feadc58) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyObject_Str [INFO] [stdout] >>> referenced by any.rs:2285 (src/types/any.rs:2285) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::str::h067d209e07a13158) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyBytes_AsString [INFO] [stdout] >>> referenced by bytes.rs:193 (src/types/bytes.rs:193) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::h64ed8ded3b8d215f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyBytes_Size [INFO] [stdout] >>> referenced by bytes.rs:194 (src/types/bytes.rs:194) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::h64ed8ded3b8d215f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyUnicode_AsUTF8AndSize [INFO] [stdout] >>> referenced by string.rs:377 (src/types/string.rs:377) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_str::hce5e462692297a9b) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyUnicode_AsEncodedString [INFO] [stdout] >>> referenced by string.rs:416 (src/types/string.rs:416) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_string_lossy::hed82ab9bac7b4577) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyType_GetName [INFO] [stdout] >>> referenced by typeobject.rs:178 (src/types/typeobject.rs:178) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..typeobject..PyType$GT$$u20$as$u20$pyo3..types..typeobject..PyTypeMethods$GT$::name::h378f94ec16f40d0f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyException_GetTraceback [INFO] [stdout] >>> referenced by err_state.rs:40 (src/err/err_state.rs:40) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::ptraceback::h725db2326fc77320) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_GetRaisedException [INFO] [stdout] >>> referenced by err_state.rs:48 (src/err/err_state.rs:48) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::take::h19b68f67ee6b7fd8) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_SetRaisedException [INFO] [stdout] >>> referenced by err_state.rs:206 (src/err/err_state.rs:206) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::PyErrState::restore::haca2fc16063856f8) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_SetString [INFO] [stdout] >>> referenced by err_state.rs:241 (src/err/err_state.rs:241) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::raise_lazy::h150c8edc64a09730) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_SetObject [INFO] [stdout] >>> referenced by err_state.rs:246 (src/err/err_state.rs:246) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::raise_lazy::h150c8edc64a09730) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyUnicode_FromStringAndSize [INFO] [stdout] >>> referenced by string.rs:167 (src/types/string.rs:167) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::types::string::PyString::new_bound::h1be2383f65fc2099) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_BaseException [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h1b6d319a7bbd627c) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h1b6d319a7bbd627c) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_OSError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hfd190deee279e0be) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hfd190deee279e0be) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_TypeError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h7ccbebe3eaea6402) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h7ccbebe3eaea6402) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_BlockingIOError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::he9438d8bf38e89ac) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::he9438d8bf38e89ac) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_BrokenPipeError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBrokenPipeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h01b488966619cdd2) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBrokenPipeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h01b488966619cdd2) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: too many errors emitted, stopping now (use --error-limit=0 to see all errors) [INFO] [stdout] collect2: error: ld returned 1 exit status [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `ggca` (example "basic") due to 1 previous error [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] [stdout] error: linking with `cc` failed: exit status: 1 [INFO] [stdout] | [INFO] [stdout] = note: "cc" "-m64" "/tmp/rustcHUn1pS/symbols.o" "<2 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libtest-*,libgetopts-*,libunicode_width-*,librustc_std_workspace_std-*}.rlib" "/opt/rustwide/target/debug/deps/{liblazy_static-509a3481d98abb23,libggca,libfast_float-f50e7f03fe3e35fc,libenv_logger-c14fd8c91b7fc71d,libatty-da15ccfbad80956e,libtermcolor-8f179e788fdc4b43,libhumantime-05b80b6cd1fafc41,libregex-55e0398aed73f152,libregex_automata-4662c386771adf4f,libaho_corasick-c3edd29732527541,libregex_syntax-6eae2ba83f4da8ae,libcsv-c2c155792aa9ec5e,libryu-ab986272b407cd41,libitoa-dceb2e2ec68b27be,libcsv_core-794db0f3d3a9fe9e,libmemchr-8483526b530fc45f,libstatrs-24037c687c986fc9,libnalgebra-ba8d522600c39321,librand_distr-ba18101014ecac97,libmatrixmultiply-78bdd29071b808a2,librawpointer-f73a58cd128df828,libnum_rational-527bb4af2a8273af,libnum_integer-eaf56f037f44b96c,libtypenum-edec2471d71e3ff6,libsimba-34e173d5bf61ed5c,libwide-fca37db65854cccb,libsafe_arch-1f8c55e704099ca9,libbytemuck-d64d7e9744cd12ae,libnum_complex-2158d2ce6fbab3b8,librand-7a4aa9d1fdcac6b4,librand_chacha-6a9818b75bb1279b,libppv_lite86-9f3414099d5801d8,librand_core-3554dbca1744bf65,libgetrandom-b51fc064ca144789,libbincode-f7697e5c8a3725db,libserde-7d338d6d62bbd6c1,liblog-17d4c04744091b72,libitertools-1910558703caedba,libpyo3-70fc57b7bf2c34f6,libmemoffset-a5a240ae285dd09a,libonce_cell-18f4b407e28e12b6,libpyo3_ffi-e49b8b2c50bfd98a,liblibc-f5c905995cce61d3,libunindent-a660ddbcf1396680,libextsort-d4e00f56949d17fa,libtempfile-33b3cc82cd8a8f5f,libfastrand-8176d9923c123d38,librustix-c831f801e7d2a5d8,libbitflags-e2ae9f1de5f0445f,liblinux_raw_sys-56cc622a5bb02e92,libcfg_if-3183e62f61f23a61,librayon-937ea05ec8e0296c,librayon_core-621f7bd31e10fa17,libcrossbeam_deque-f2c3fd5e7bbfd927,libcrossbeam_epoch-ed4a2d3daceac61a,libcrossbeam_utils-70904e6a5a5294cc,libeither-e3ab338dd559fca0,libapprox-9ca7c1181f1a7a2b,libnum_traits-cfc634d4f0a04bcf}.rlib" "/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libstd-*,libpanic_unwind-*,libobject-*,libmemchr-*,libaddr2line-*,libgimli-*,librustc_demangle-*,libstd_detect-*,libhashbrown-*,librustc_std_workspace_alloc-*,libminiz_oxide-*,libadler2-*,libunwind-*,libcfg_if-*,liblibc-*,librustc_std_workspace_core-*,liballoc-*,libcore-*,libcompiler_builtins-*}.rlib" "-Wl,-Bdynamic" "-lgcc_s" "-lutil" "-lrt" "-lpthread" "-lm" "-ldl" "-lc" "-L" "/tmp/rustcHUn1pS/raw-dylibs" "-B/lib/rustlib/x86_64-unknown-linux-gnu/bin/gcc-ld" "-fuse-ld=lld" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/opt/rustwide/target/debug/deps/cpg_site_ids-4baff4f5c12c90b1" "-Wl,--gc-sections" "-pie" "-Wl,-z,relro,-z,now" "-nodefaultlibs" [INFO] [stdout] = note: some arguments are omitted. use `--verbose` to show all linker arguments [INFO] [stdout] = note: rust-lld: error: undefined symbol: PyExc_Exception [INFO] [stdout] >>> referenced by exceptions.rs:309 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-0.22.2/src/exceptions.rs:309) [INFO] [stdout] >>> ggca.ggca.175a4e69c89838ca-cgu.14.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::had7df04b87b7cbfd) in archive /opt/rustwide/target/debug/deps/libggca.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-0.22.2/src/exceptions.rs:309) [INFO] [stdout] >>> ggca.ggca.175a4e69c89838ca-cgu.14.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::had7df04b87b7cbfd) in archive /opt/rustwide/target/debug/deps/libggca.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: _Py_Dealloc [INFO] [stdout] >>> referenced by object.rs:611 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-ffi-0.22.2/src/object.rs:611) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h2f26f0aed5f89c8f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by object.rs:611 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-ffi-0.22.2/src/object.rs:611) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h88b27dc260f2fdea) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by object.rs:611 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-ffi-0.22.2/src/object.rs:611) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::hc2ba13d66f24e9d9) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced 4 more times [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyObject_Repr [INFO] [stdout] >>> referenced by any.rs:2277 (src/types/any.rs:2277) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::repr::h865265723feadc58) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyObject_Str [INFO] [stdout] >>> referenced by any.rs:2285 (src/types/any.rs:2285) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::str::h067d209e07a13158) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyBytes_AsString [INFO] [stdout] >>> referenced by bytes.rs:193 (src/types/bytes.rs:193) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::h64ed8ded3b8d215f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyBytes_Size [INFO] [stdout] >>> referenced by bytes.rs:194 (src/types/bytes.rs:194) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::h64ed8ded3b8d215f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyUnicode_AsUTF8AndSize [INFO] [stdout] >>> referenced by string.rs:377 (src/types/string.rs:377) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_str::hce5e462692297a9b) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyUnicode_AsEncodedString [INFO] [stdout] >>> referenced by string.rs:416 (src/types/string.rs:416) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_string_lossy::hed82ab9bac7b4577) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyType_GetName [INFO] [stdout] >>> referenced by typeobject.rs:178 (src/types/typeobject.rs:178) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..typeobject..PyType$GT$$u20$as$u20$pyo3..types..typeobject..PyTypeMethods$GT$::name::h378f94ec16f40d0f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyException_GetTraceback [INFO] [stdout] >>> referenced by err_state.rs:40 (src/err/err_state.rs:40) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::ptraceback::h725db2326fc77320) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_GetRaisedException [INFO] [stdout] >>> referenced by err_state.rs:48 (src/err/err_state.rs:48) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::take::h19b68f67ee6b7fd8) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_SetRaisedException [INFO] [stdout] >>> referenced by err_state.rs:206 (src/err/err_state.rs:206) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::PyErrState::restore::haca2fc16063856f8) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_SetString [INFO] [stdout] >>> referenced by err_state.rs:241 (src/err/err_state.rs:241) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::raise_lazy::h150c8edc64a09730) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_SetObject [INFO] [stdout] >>> referenced by err_state.rs:246 (src/err/err_state.rs:246) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::raise_lazy::h150c8edc64a09730) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyUnicode_FromStringAndSize [INFO] [stdout] >>> referenced by string.rs:167 (src/types/string.rs:167) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::types::string::PyString::new_bound::h1be2383f65fc2099) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_BaseException [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h1b6d319a7bbd627c) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h1b6d319a7bbd627c) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_OSError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hfd190deee279e0be) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hfd190deee279e0be) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_TypeError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h7ccbebe3eaea6402) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h7ccbebe3eaea6402) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_BlockingIOError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::he9438d8bf38e89ac) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::he9438d8bf38e89ac) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_BrokenPipeError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBrokenPipeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h01b488966619cdd2) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBrokenPipeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h01b488966619cdd2) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: too many errors emitted, stopping now (use --error-limit=0 to see all errors) [INFO] [stdout] collect2: error: ld returned 1 exit status [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `ggca` (test "cpg_site_ids") due to 1 previous error [INFO] [stdout] error: linking with `cc` failed: exit status: 1 [INFO] [stdout] | [INFO] [stdout] = note: "cc" "-m64" "/tmp/rustcpHJMoD/symbols.o" "<4 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libtest-*,libgetopts-*,libunicode_width-*,librustc_std_workspace_std-*}.rlib" "/opt/rustwide/target/debug/deps/{liblazy_static-509a3481d98abb23,libggca,libfast_float-f50e7f03fe3e35fc,libenv_logger-c14fd8c91b7fc71d,libatty-da15ccfbad80956e,libtermcolor-8f179e788fdc4b43,libhumantime-05b80b6cd1fafc41,libregex-55e0398aed73f152,libregex_automata-4662c386771adf4f,libaho_corasick-c3edd29732527541,libregex_syntax-6eae2ba83f4da8ae,libcsv-c2c155792aa9ec5e,libryu-ab986272b407cd41,libitoa-dceb2e2ec68b27be,libcsv_core-794db0f3d3a9fe9e,libmemchr-8483526b530fc45f,libstatrs-24037c687c986fc9,libnalgebra-ba8d522600c39321,librand_distr-ba18101014ecac97,libmatrixmultiply-78bdd29071b808a2,librawpointer-f73a58cd128df828,libnum_rational-527bb4af2a8273af,libnum_integer-eaf56f037f44b96c,libtypenum-edec2471d71e3ff6,libsimba-34e173d5bf61ed5c,libwide-fca37db65854cccb,libsafe_arch-1f8c55e704099ca9,libbytemuck-d64d7e9744cd12ae,libnum_complex-2158d2ce6fbab3b8,librand-7a4aa9d1fdcac6b4,librand_chacha-6a9818b75bb1279b,libppv_lite86-9f3414099d5801d8,librand_core-3554dbca1744bf65,libgetrandom-b51fc064ca144789,libbincode-f7697e5c8a3725db,libserde-7d338d6d62bbd6c1,liblog-17d4c04744091b72,libitertools-1910558703caedba,libpyo3-70fc57b7bf2c34f6,libmemoffset-a5a240ae285dd09a,libonce_cell-18f4b407e28e12b6,libpyo3_ffi-e49b8b2c50bfd98a,liblibc-f5c905995cce61d3,libunindent-a660ddbcf1396680,libextsort-d4e00f56949d17fa,libtempfile-33b3cc82cd8a8f5f,libfastrand-8176d9923c123d38,librustix-c831f801e7d2a5d8,libbitflags-e2ae9f1de5f0445f,liblinux_raw_sys-56cc622a5bb02e92,libcfg_if-3183e62f61f23a61,librayon-937ea05ec8e0296c,librayon_core-621f7bd31e10fa17,libcrossbeam_deque-f2c3fd5e7bbfd927,libcrossbeam_epoch-ed4a2d3daceac61a,libcrossbeam_utils-70904e6a5a5294cc,libeither-e3ab338dd559fca0,libapprox-9ca7c1181f1a7a2b,libnum_traits-cfc634d4f0a04bcf}.rlib" "/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libstd-*,libpanic_unwind-*,libobject-*,libmemchr-*,libaddr2line-*,libgimli-*,librustc_demangle-*,libstd_detect-*,libhashbrown-*,librustc_std_workspace_alloc-*,libminiz_oxide-*,libadler2-*,libunwind-*,libcfg_if-*,liblibc-*,librustc_std_workspace_core-*,liballoc-*,libcore-*,libcompiler_builtins-*}.rlib" "-Wl,-Bdynamic" "-lgcc_s" "-lutil" "-lrt" "-lpthread" "-lm" "-ldl" "-lc" "-L" "/tmp/rustcpHJMoD/raw-dylibs" "-B/lib/rustlib/x86_64-unknown-linux-gnu/bin/gcc-ld" "-fuse-ld=lld" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/opt/rustwide/target/debug/deps/pearson-e9d8334c3994dbf6" "-Wl,--gc-sections" "-pie" "-Wl,-z,relro,-z,now" "-nodefaultlibs" [INFO] [stdout] = note: some arguments are omitted. use `--verbose` to show all linker arguments [INFO] [stdout] = note: rust-lld: error: undefined symbol: PyExc_Exception [INFO] [stdout] >>> referenced by exceptions.rs:309 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-0.22.2/src/exceptions.rs:309) [INFO] [stdout] >>> ggca.ggca.175a4e69c89838ca-cgu.14.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::had7df04b87b7cbfd) in archive /opt/rustwide/target/debug/deps/libggca.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-0.22.2/src/exceptions.rs:309) [INFO] [stdout] >>> ggca.ggca.175a4e69c89838ca-cgu.14.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::had7df04b87b7cbfd) in archive /opt/rustwide/target/debug/deps/libggca.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: _Py_Dealloc [INFO] [stdout] >>> referenced by object.rs:611 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-ffi-0.22.2/src/object.rs:611) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h2f26f0aed5f89c8f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by object.rs:611 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-ffi-0.22.2/src/object.rs:611) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h88b27dc260f2fdea) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by object.rs:611 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-ffi-0.22.2/src/object.rs:611) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::hc2ba13d66f24e9d9) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced 4 more times [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyObject_Repr [INFO] [stdout] >>> referenced by any.rs:2277 (src/types/any.rs:2277) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::repr::h865265723feadc58) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyObject_Str [INFO] [stdout] >>> referenced by any.rs:2285 (src/types/any.rs:2285) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::str::h067d209e07a13158) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyBytes_AsString [INFO] [stdout] >>> referenced by bytes.rs:193 (src/types/bytes.rs:193) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::h64ed8ded3b8d215f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyBytes_Size [INFO] [stdout] >>> referenced by bytes.rs:194 (src/types/bytes.rs:194) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::h64ed8ded3b8d215f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyUnicode_AsUTF8AndSize [INFO] [stdout] >>> referenced by string.rs:377 (src/types/string.rs:377) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_str::hce5e462692297a9b) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyUnicode_AsEncodedString [INFO] [stdout] >>> referenced by string.rs:416 (src/types/string.rs:416) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_string_lossy::hed82ab9bac7b4577) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyType_GetName [INFO] [stdout] >>> referenced by typeobject.rs:178 (src/types/typeobject.rs:178) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..typeobject..PyType$GT$$u20$as$u20$pyo3..types..typeobject..PyTypeMethods$GT$::name::h378f94ec16f40d0f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyException_GetTraceback [INFO] [stdout] >>> referenced by err_state.rs:40 (src/err/err_state.rs:40) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::ptraceback::h725db2326fc77320) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_GetRaisedException [INFO] [stdout] >>> referenced by err_state.rs:48 (src/err/err_state.rs:48) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::take::h19b68f67ee6b7fd8) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_SetRaisedException [INFO] [stdout] >>> referenced by err_state.rs:206 (src/err/err_state.rs:206) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::PyErrState::restore::haca2fc16063856f8) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_SetString [INFO] [stdout] >>> referenced by err_state.rs:241 (src/err/err_state.rs:241) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::raise_lazy::h150c8edc64a09730) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_SetObject [INFO] [stdout] >>> referenced by err_state.rs:246 (src/err/err_state.rs:246) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::raise_lazy::h150c8edc64a09730) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyUnicode_FromStringAndSize [INFO] [stdout] >>> referenced by string.rs:167 (src/types/string.rs:167) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::types::string::PyString::new_bound::h1be2383f65fc2099) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_BaseException [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h1b6d319a7bbd627c) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h1b6d319a7bbd627c) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_OSError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hfd190deee279e0be) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hfd190deee279e0be) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_TypeError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h7ccbebe3eaea6402) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h7ccbebe3eaea6402) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_BlockingIOError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::he9438d8bf38e89ac) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::he9438d8bf38e89ac) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_BrokenPipeError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBrokenPipeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h01b488966619cdd2) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBrokenPipeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h01b488966619cdd2) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: too many errors emitted, stopping now (use --error-limit=0 to see all errors) [INFO] [stdout] collect2: error: ld returned 1 exit status [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: linking with `cc` failed: exit status: 1 [INFO] [stdout] | [INFO] [stdout] = note: "cc" "-m64" "/tmp/rustcgxLkF8/symbols.o" "<2 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "/opt/rustwide/target/debug/deps/{libggca,libfast_float-f50e7f03fe3e35fc,libenv_logger-c14fd8c91b7fc71d,libatty-da15ccfbad80956e,libtermcolor-8f179e788fdc4b43,libhumantime-05b80b6cd1fafc41,libregex-55e0398aed73f152,libregex_automata-4662c386771adf4f,libaho_corasick-c3edd29732527541,libregex_syntax-6eae2ba83f4da8ae,libcsv-c2c155792aa9ec5e,libryu-ab986272b407cd41,libitoa-dceb2e2ec68b27be,libcsv_core-794db0f3d3a9fe9e,libmemchr-8483526b530fc45f,libstatrs-24037c687c986fc9,libnalgebra-ba8d522600c39321,librand_distr-ba18101014ecac97,libmatrixmultiply-78bdd29071b808a2,librawpointer-f73a58cd128df828,libnum_rational-527bb4af2a8273af,libnum_integer-eaf56f037f44b96c,libtypenum-edec2471d71e3ff6,libsimba-34e173d5bf61ed5c,libwide-fca37db65854cccb,libsafe_arch-1f8c55e704099ca9,libbytemuck-d64d7e9744cd12ae,libnum_complex-2158d2ce6fbab3b8,librand-7a4aa9d1fdcac6b4,librand_chacha-6a9818b75bb1279b,libppv_lite86-9f3414099d5801d8,librand_core-3554dbca1744bf65,libgetrandom-b51fc064ca144789,libapprox-9ca7c1181f1a7a2b,libnum_traits-cfc634d4f0a04bcf,libbincode-f7697e5c8a3725db,libserde-7d338d6d62bbd6c1,liblog-17d4c04744091b72,libitertools-1910558703caedba,libpyo3-70fc57b7bf2c34f6,libmemoffset-a5a240ae285dd09a,libonce_cell-18f4b407e28e12b6,libpyo3_ffi-e49b8b2c50bfd98a,liblibc-f5c905995cce61d3,libunindent-a660ddbcf1396680,libextsort-d4e00f56949d17fa,libtempfile-33b3cc82cd8a8f5f,libfastrand-8176d9923c123d38,librustix-c831f801e7d2a5d8,libbitflags-e2ae9f1de5f0445f,liblinux_raw_sys-56cc622a5bb02e92,libcfg_if-3183e62f61f23a61,librayon-937ea05ec8e0296c,librayon_core-621f7bd31e10fa17,libcrossbeam_deque-f2c3fd5e7bbfd927,libcrossbeam_epoch-ed4a2d3daceac61a,libcrossbeam_utils-70904e6a5a5294cc,libeither-e3ab338dd559fca0}.rlib" "/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libstd-*,libpanic_unwind-*,libobject-*,libmemchr-*,libaddr2line-*,libgimli-*,librustc_demangle-*,libstd_detect-*,libhashbrown-*,librustc_std_workspace_alloc-*,libminiz_oxide-*,libadler2-*,libunwind-*,libcfg_if-*,liblibc-*,librustc_std_workspace_core-*,liballoc-*,libcore-*,libcompiler_builtins-*}.rlib" "-Wl,-Bdynamic" "-lgcc_s" "-lutil" "-lrt" "-lpthread" "-lm" "-ldl" "-lc" "-L" "/tmp/rustcgxLkF8/raw-dylibs" "-B/lib/rustlib/x86_64-unknown-linux-gnu/bin/gcc-ld" "-fuse-ld=lld" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/opt/rustwide/target/debug/examples/cpg_site_ids-ca604444ebe05a11" "-Wl,--gc-sections" "-pie" "-Wl,-z,relro,-z,now" "-nodefaultlibs" [INFO] [stdout] = note: some arguments are omitted. use `--verbose` to show all linker arguments [INFO] [stdout] = note: rust-lld: error: undefined symbol: PyExc_Exception [INFO] [stdout] >>> referenced by exceptions.rs:309 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-0.22.2/src/exceptions.rs:309) [INFO] [stdout] >>> ggca.ggca.175a4e69c89838ca-cgu.14.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::had7df04b87b7cbfd) in archive /opt/rustwide/target/debug/deps/libggca.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-0.22.2/src/exceptions.rs:309) [INFO] [stdout] >>> ggca.ggca.175a4e69c89838ca-cgu.14.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::had7df04b87b7cbfd) in archive /opt/rustwide/target/debug/deps/libggca.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: _Py_Dealloc [INFO] [stdout] >>> referenced by object.rs:611 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-ffi-0.22.2/src/object.rs:611) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h2f26f0aed5f89c8f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by object.rs:611 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-ffi-0.22.2/src/object.rs:611) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h88b27dc260f2fdea) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by object.rs:611 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-ffi-0.22.2/src/object.rs:611) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::hc2ba13d66f24e9d9) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced 4 more times [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyObject_Repr [INFO] [stdout] >>> referenced by any.rs:2277 (src/types/any.rs:2277) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::repr::h865265723feadc58) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyObject_Str [INFO] [stdout] >>> referenced by any.rs:2285 (src/types/any.rs:2285) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::str::h067d209e07a13158) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyBytes_AsString [INFO] [stdout] >>> referenced by bytes.rs:193 (src/types/bytes.rs:193) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::h64ed8ded3b8d215f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyBytes_Size [INFO] [stdout] >>> referenced by bytes.rs:194 (src/types/bytes.rs:194) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::h64ed8ded3b8d215f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyUnicode_AsUTF8AndSize [INFO] [stdout] >>> referenced by string.rs:377 (src/types/string.rs:377) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_str::hce5e462692297a9b) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyUnicode_AsEncodedString [INFO] [stdout] >>> referenced by string.rs:416 (src/types/string.rs:416) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_string_lossy::hed82ab9bac7b4577) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyType_GetName [INFO] [stdout] >>> referenced by typeobject.rs:178 (src/types/typeobject.rs:178) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..typeobject..PyType$GT$$u20$as$u20$pyo3..types..typeobject..PyTypeMethods$GT$::name::h378f94ec16f40d0f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyException_GetTraceback [INFO] [stdout] >>> referenced by err_state.rs:40 (src/err/err_state.rs:40) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::ptraceback::h725db2326fc77320) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_GetRaisedException [INFO] [stdout] >>> referenced by err_state.rs:48 (src/err/err_state.rs:48) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::take::h19b68f67ee6b7fd8) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_SetRaisedException [INFO] [stdout] >>> referenced by err_state.rs:206 (src/err/err_state.rs:206) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::PyErrState::restore::haca2fc16063856f8) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_SetString [INFO] [stdout] >>> referenced by err_state.rs:241 (src/err/err_state.rs:241) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::raise_lazy::h150c8edc64a09730) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_SetObject [INFO] [stdout] >>> referenced by err_state.rs:246 (src/err/err_state.rs:246) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::raise_lazy::h150c8edc64a09730) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyUnicode_FromStringAndSize [INFO] [stdout] >>> referenced by string.rs:167 (src/types/string.rs:167) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::types::string::PyString::new_bound::h1be2383f65fc2099) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_BaseException [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h1b6d319a7bbd627c) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h1b6d319a7bbd627c) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_OSError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hfd190deee279e0be) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hfd190deee279e0be) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_TypeError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h7ccbebe3eaea6402) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h7ccbebe3eaea6402) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_BlockingIOError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::he9438d8bf38e89ac) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::he9438d8bf38e89ac) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_BrokenPipeError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBrokenPipeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h01b488966619cdd2) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBrokenPipeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h01b488966619cdd2) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: too many errors emitted, stopping now (use --error-limit=0 to see all errors) [INFO] [stdout] collect2: error: ld returned 1 exit status [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `ggca` (example "cpg_site_ids") due to 1 previous error [INFO] [stderr] error: could not compile `ggca` (test "pearson") due to 1 previous error [INFO] [stdout] error: linking with `cc` failed: exit status: 1 [INFO] [stdout] | [INFO] [stdout] = note: "cc" "-m64" "/tmp/rustcelZ2ct/symbols.o" "<2 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libtest-*,libgetopts-*,libunicode_width-*,librustc_std_workspace_std-*}.rlib" "/opt/rustwide/target/debug/deps/{libggca,libfast_float-f50e7f03fe3e35fc,libenv_logger-c14fd8c91b7fc71d,libatty-da15ccfbad80956e,libtermcolor-8f179e788fdc4b43,libhumantime-05b80b6cd1fafc41,libregex-55e0398aed73f152,libregex_automata-4662c386771adf4f,libaho_corasick-c3edd29732527541,libregex_syntax-6eae2ba83f4da8ae,libcsv-c2c155792aa9ec5e,libryu-ab986272b407cd41,libitoa-dceb2e2ec68b27be,libcsv_core-794db0f3d3a9fe9e,libmemchr-8483526b530fc45f,libstatrs-24037c687c986fc9,libnalgebra-ba8d522600c39321,librand_distr-ba18101014ecac97,libmatrixmultiply-78bdd29071b808a2,librawpointer-f73a58cd128df828,libnum_rational-527bb4af2a8273af,libnum_integer-eaf56f037f44b96c,libtypenum-edec2471d71e3ff6,libsimba-34e173d5bf61ed5c,libwide-fca37db65854cccb,libsafe_arch-1f8c55e704099ca9,libbytemuck-d64d7e9744cd12ae,libnum_complex-2158d2ce6fbab3b8,librand-7a4aa9d1fdcac6b4,librand_chacha-6a9818b75bb1279b,libppv_lite86-9f3414099d5801d8,librand_core-3554dbca1744bf65,libgetrandom-b51fc064ca144789,libbincode-f7697e5c8a3725db,libserde-7d338d6d62bbd6c1,liblog-17d4c04744091b72,libitertools-1910558703caedba,libpyo3-70fc57b7bf2c34f6,libmemoffset-a5a240ae285dd09a,libonce_cell-18f4b407e28e12b6,libpyo3_ffi-e49b8b2c50bfd98a,liblibc-f5c905995cce61d3,libunindent-a660ddbcf1396680,libextsort-d4e00f56949d17fa,libtempfile-33b3cc82cd8a8f5f,libfastrand-8176d9923c123d38,librustix-c831f801e7d2a5d8,libbitflags-e2ae9f1de5f0445f,liblinux_raw_sys-56cc622a5bb02e92,libcfg_if-3183e62f61f23a61,librayon-937ea05ec8e0296c,librayon_core-621f7bd31e10fa17,libcrossbeam_deque-f2c3fd5e7bbfd927,libcrossbeam_epoch-ed4a2d3daceac61a,libcrossbeam_utils-70904e6a5a5294cc,libeither-e3ab338dd559fca0,libapprox-9ca7c1181f1a7a2b,libnum_traits-cfc634d4f0a04bcf}.rlib" "/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libstd-*,libpanic_unwind-*,libobject-*,libmemchr-*,libaddr2line-*,libgimli-*,librustc_demangle-*,libstd_detect-*,libhashbrown-*,librustc_std_workspace_alloc-*,libminiz_oxide-*,libadler2-*,libunwind-*,libcfg_if-*,liblibc-*,librustc_std_workspace_core-*,liballoc-*,libcore-*,libcompiler_builtins-*}.rlib" "-Wl,-Bdynamic" "-lgcc_s" "-lutil" "-lrt" "-lpthread" "-lm" "-ldl" "-lc" "-L" "/tmp/rustcelZ2ct/raw-dylibs" "-B/lib/rustlib/x86_64-unknown-linux-gnu/bin/gcc-ld" "-fuse-ld=lld" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/opt/rustwide/target/debug/deps/nan_filtering-b404a5da4875b947" "-Wl,--gc-sections" "-pie" "-Wl,-z,relro,-z,now" "-nodefaultlibs" [INFO] [stdout] = note: some arguments are omitted. use `--verbose` to show all linker arguments [INFO] [stdout] = note: rust-lld: error: undefined symbol: PyExc_Exception [INFO] [stdout] >>> referenced by exceptions.rs:309 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-0.22.2/src/exceptions.rs:309) [INFO] [stdout] >>> ggca.ggca.175a4e69c89838ca-cgu.14.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::had7df04b87b7cbfd) in archive /opt/rustwide/target/debug/deps/libggca.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-0.22.2/src/exceptions.rs:309) [INFO] [stdout] >>> ggca.ggca.175a4e69c89838ca-cgu.14.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::had7df04b87b7cbfd) in archive /opt/rustwide/target/debug/deps/libggca.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_PrintEx [INFO] [stdout] >>> referenced by mod.rs:474 (src/err/mod.rs:474) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.13.rcgu.o:(pyo3::err::PyErr::print_panic_and_unwind::h81ec8c80b0e662ee) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_NewExceptionWithDoc [INFO] [stdout] >>> referenced by mod.rs:569 (src/err/mod.rs:569) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.13.rcgu.o:(pyo3::err::PyErr::new_type_bound::hc161480b3ed1cce7) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_WriteUnraisable [INFO] [stdout] >>> referenced by mod.rs:709 (src/err/mod.rs:709) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.13.rcgu.o:(pyo3::err::PyErr::write_unraisable_bound::h9d2c2b299ba7d754) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_Print [INFO] [stdout] >>> referenced by mod.rs:1081 (src/err/mod.rs:1081) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.13.rcgu.o:(pyo3::err::panic_after_error::h4eb9c99d96ae5061) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: Py_IsInitialized [INFO] [stdout] >>> referenced by gil.rs:80 (src/gil.rs:80) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.10.rcgu.o:(pyo3::gil::prepare_freethreaded_python::_$u7b$$u7b$closure$u7d$$u7d$::h5610153f6fd5ac47) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by gil.rs:199 (src/gil.rs:199) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.10.rcgu.o:(pyo3::gil::GILGuard::acquire::_$u7b$$u7b$closure$u7d$$u7d$::h4199ed4b7fdfa143) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: Py_InitializeEx [INFO] [stdout] >>> referenced by gil.rs:81 (src/gil.rs:81) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.10.rcgu.o:(pyo3::gil::prepare_freethreaded_python::_$u7b$$u7b$closure$u7d$$u7d$::h5610153f6fd5ac47) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyEval_SaveThread [INFO] [stdout] >>> referenced by gil.rs:84 (src/gil.rs:84) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.10.rcgu.o:(pyo3::gil::prepare_freethreaded_python::_$u7b$$u7b$closure$u7d$$u7d$::h5610153f6fd5ac47) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyGILState_Ensure [INFO] [stdout] >>> referenced by gil.rs:224 (src/gil.rs:224) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.10.rcgu.o:(pyo3::gil::GILGuard::acquire_unchecked::ha0a0d7839ada4fc6) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyGILState_Release [INFO] [stdout] >>> referenced by gil.rs:273 (src/gil.rs:273) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.10.rcgu.o:(_$LT$pyo3..gil..GILGuard$u20$as$u20$core..ops..drop..Drop$GT$::drop::he302a19363cea196) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: _Py_Dealloc [INFO] [stdout] >>> referenced by object.rs:611 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-ffi-0.22.2/src/object.rs:611) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.10.rcgu.o:(pyo3::gil::ReferencePool::update_counts::h98a3802c1842e76b) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by object.rs:611 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-ffi-0.22.2/src/object.rs:611) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.10.rcgu.o:(pyo3::gil::register_decref::h493b4d01d5949c36) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by object.rs:611 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-ffi-0.22.2/src/object.rs:611) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h2f26f0aed5f89c8f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced 4 more times [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyException_GetTraceback [INFO] [stdout] >>> referenced by err_state.rs:40 (src/err/err_state.rs:40) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::ptraceback::h725db2326fc77320) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_GetRaisedException [INFO] [stdout] >>> referenced by err_state.rs:48 (src/err/err_state.rs:48) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::take::h19b68f67ee6b7fd8) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_SetRaisedException [INFO] [stdout] >>> referenced by err_state.rs:206 (src/err/err_state.rs:206) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::PyErrState::restore::haca2fc16063856f8) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_SetString [INFO] [stdout] >>> referenced by err_state.rs:241 (src/err/err_state.rs:241) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::raise_lazy::h150c8edc64a09730) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_SetObject [INFO] [stdout] >>> referenced by err_state.rs:246 (src/err/err_state.rs:246) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::raise_lazy::h150c8edc64a09730) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyUnicode_FromStringAndSize [INFO] [stdout] >>> referenced by string.rs:167 (src/types/string.rs:167) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::types::string::PyString::new_bound::h1be2383f65fc2099) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_BaseException [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h1b6d319a7bbd627c) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h1b6d319a7bbd627c) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_OSError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hfd190deee279e0be) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hfd190deee279e0be) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_TypeError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h7ccbebe3eaea6402) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h7ccbebe3eaea6402) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: too many errors emitted, stopping now (use --error-limit=0 to see all errors) [INFO] [stdout] collect2: error: ld returned 1 exit status [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `ggca` (test "nan_filtering") due to 1 previous error [INFO] [stdout] error: linking with `cc` failed: exit status: 1 [INFO] [stdout] | [INFO] [stdout] = note: "cc" "-m64" "/tmp/rustcOR3FRV/symbols.o" "<5 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libtest-*,libgetopts-*,libunicode_width-*,librustc_std_workspace_std-*}.rlib" "/opt/rustwide/target/debug/deps/{liblazy_static-509a3481d98abb23,libggca,libfast_float-f50e7f03fe3e35fc,libenv_logger-c14fd8c91b7fc71d,libatty-da15ccfbad80956e,libtermcolor-8f179e788fdc4b43,libhumantime-05b80b6cd1fafc41,libregex-55e0398aed73f152,libregex_automata-4662c386771adf4f,libaho_corasick-c3edd29732527541,libregex_syntax-6eae2ba83f4da8ae,libcsv-c2c155792aa9ec5e,libryu-ab986272b407cd41,libitoa-dceb2e2ec68b27be,libcsv_core-794db0f3d3a9fe9e,libmemchr-8483526b530fc45f,libstatrs-24037c687c986fc9,libnalgebra-ba8d522600c39321,librand_distr-ba18101014ecac97,libmatrixmultiply-78bdd29071b808a2,librawpointer-f73a58cd128df828,libnum_rational-527bb4af2a8273af,libnum_integer-eaf56f037f44b96c,libtypenum-edec2471d71e3ff6,libsimba-34e173d5bf61ed5c,libwide-fca37db65854cccb,libsafe_arch-1f8c55e704099ca9,libbytemuck-d64d7e9744cd12ae,libnum_complex-2158d2ce6fbab3b8,librand-7a4aa9d1fdcac6b4,librand_chacha-6a9818b75bb1279b,libppv_lite86-9f3414099d5801d8,librand_core-3554dbca1744bf65,libgetrandom-b51fc064ca144789,libbincode-f7697e5c8a3725db,libserde-7d338d6d62bbd6c1,liblog-17d4c04744091b72,libitertools-1910558703caedba,libpyo3-70fc57b7bf2c34f6,libmemoffset-a5a240ae285dd09a,libonce_cell-18f4b407e28e12b6,libpyo3_ffi-e49b8b2c50bfd98a,liblibc-f5c905995cce61d3,libunindent-a660ddbcf1396680,libextsort-d4e00f56949d17fa,libtempfile-33b3cc82cd8a8f5f,libfastrand-8176d9923c123d38,librustix-c831f801e7d2a5d8,libbitflags-e2ae9f1de5f0445f,liblinux_raw_sys-56cc622a5bb02e92,libcfg_if-3183e62f61f23a61,librayon-937ea05ec8e0296c,librayon_core-621f7bd31e10fa17,libcrossbeam_deque-f2c3fd5e7bbfd927,libcrossbeam_epoch-ed4a2d3daceac61a,libcrossbeam_utils-70904e6a5a5294cc,libeither-e3ab338dd559fca0,libapprox-9ca7c1181f1a7a2b,libnum_traits-cfc634d4f0a04bcf}.rlib" "/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libstd-*,libpanic_unwind-*,libobject-*,libmemchr-*,libaddr2line-*,libgimli-*,librustc_demangle-*,libstd_detect-*,libhashbrown-*,librustc_std_workspace_alloc-*,libminiz_oxide-*,libadler2-*,libunwind-*,libcfg_if-*,liblibc-*,librustc_std_workspace_core-*,liballoc-*,libcore-*,libcompiler_builtins-*}.rlib" "-Wl,-Bdynamic" "-lgcc_s" "-lutil" "-lrt" "-lpthread" "-lm" "-ldl" "-lc" "-L" "/tmp/rustcOR3FRV/raw-dylibs" "-B/lib/rustlib/x86_64-unknown-linux-gnu/bin/gcc-ld" "-fuse-ld=lld" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/opt/rustwide/target/debug/deps/kendall-52b593845a2d25e6" "-Wl,--gc-sections" "-pie" "-Wl,-z,relro,-z,now" "-nodefaultlibs" [INFO] [stdout] = note: some arguments are omitted. use `--verbose` to show all linker arguments [INFO] [stdout] = note: rust-lld: error: undefined symbol: PyExc_Exception [INFO] [stdout] >>> referenced by exceptions.rs:309 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-0.22.2/src/exceptions.rs:309) [INFO] [stdout] >>> ggca.ggca.175a4e69c89838ca-cgu.14.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::had7df04b87b7cbfd) in archive /opt/rustwide/target/debug/deps/libggca.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-0.22.2/src/exceptions.rs:309) [INFO] [stdout] >>> ggca.ggca.175a4e69c89838ca-cgu.14.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::had7df04b87b7cbfd) in archive /opt/rustwide/target/debug/deps/libggca.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: _Py_Dealloc [INFO] [stdout] >>> referenced by object.rs:611 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-ffi-0.22.2/src/object.rs:611) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h2f26f0aed5f89c8f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by object.rs:611 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-ffi-0.22.2/src/object.rs:611) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h88b27dc260f2fdea) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by object.rs:611 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-ffi-0.22.2/src/object.rs:611) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::hc2ba13d66f24e9d9) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced 4 more times [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyObject_Repr [INFO] [stdout] >>> referenced by any.rs:2277 (src/types/any.rs:2277) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::repr::h865265723feadc58) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyObject_Str [INFO] [stdout] >>> referenced by any.rs:2285 (src/types/any.rs:2285) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::str::h067d209e07a13158) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyBytes_AsString [INFO] [stdout] >>> referenced by bytes.rs:193 (src/types/bytes.rs:193) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::h64ed8ded3b8d215f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyBytes_Size [INFO] [stdout] >>> referenced by bytes.rs:194 (src/types/bytes.rs:194) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::h64ed8ded3b8d215f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyUnicode_AsUTF8AndSize [INFO] [stdout] >>> referenced by string.rs:377 (src/types/string.rs:377) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_str::hce5e462692297a9b) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyUnicode_AsEncodedString [INFO] [stdout] >>> referenced by string.rs:416 (src/types/string.rs:416) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_string_lossy::hed82ab9bac7b4577) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyType_GetName [INFO] [stdout] >>> referenced by typeobject.rs:178 (src/types/typeobject.rs:178) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..typeobject..PyType$GT$$u20$as$u20$pyo3..types..typeobject..PyTypeMethods$GT$::name::h378f94ec16f40d0f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyException_GetTraceback [INFO] [stdout] >>> referenced by err_state.rs:40 (src/err/err_state.rs:40) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::ptraceback::h725db2326fc77320) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_GetRaisedException [INFO] [stdout] >>> referenced by err_state.rs:48 (src/err/err_state.rs:48) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::take::h19b68f67ee6b7fd8) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_SetRaisedException [INFO] [stdout] >>> referenced by err_state.rs:206 (src/err/err_state.rs:206) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::PyErrState::restore::haca2fc16063856f8) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_SetString [INFO] [stdout] >>> referenced by err_state.rs:241 (src/err/err_state.rs:241) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::raise_lazy::h150c8edc64a09730) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_SetObject [INFO] [stdout] >>> referenced by err_state.rs:246 (src/err/err_state.rs:246) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::raise_lazy::h150c8edc64a09730) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyUnicode_FromStringAndSize [INFO] [stdout] >>> referenced by string.rs:167 (src/types/string.rs:167) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::types::string::PyString::new_bound::h1be2383f65fc2099) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_BaseException [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h1b6d319a7bbd627c) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h1b6d319a7bbd627c) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_OSError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hfd190deee279e0be) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hfd190deee279e0be) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_TypeError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h7ccbebe3eaea6402) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h7ccbebe3eaea6402) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_BlockingIOError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::he9438d8bf38e89ac) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::he9438d8bf38e89ac) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_BrokenPipeError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBrokenPipeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h01b488966619cdd2) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBrokenPipeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h01b488966619cdd2) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: too many errors emitted, stopping now (use --error-limit=0 to see all errors) [INFO] [stdout] collect2: error: ld returned 1 exit status [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: linking with `cc` failed: exit status: 1 [INFO] [stdout] | [INFO] [stdout] = note: "cc" "-m64" "/tmp/rustcyEDj04/symbols.o" "<5 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libtest-*,libgetopts-*,libunicode_width-*,librustc_std_workspace_std-*}.rlib" "/opt/rustwide/target/debug/deps/{liblazy_static-509a3481d98abb23,libggca,libfast_float-f50e7f03fe3e35fc,libenv_logger-c14fd8c91b7fc71d,libatty-da15ccfbad80956e,libtermcolor-8f179e788fdc4b43,libhumantime-05b80b6cd1fafc41,libregex-55e0398aed73f152,libregex_automata-4662c386771adf4f,libaho_corasick-c3edd29732527541,libregex_syntax-6eae2ba83f4da8ae,libcsv-c2c155792aa9ec5e,libryu-ab986272b407cd41,libitoa-dceb2e2ec68b27be,libcsv_core-794db0f3d3a9fe9e,libmemchr-8483526b530fc45f,libstatrs-24037c687c986fc9,libnalgebra-ba8d522600c39321,librand_distr-ba18101014ecac97,libmatrixmultiply-78bdd29071b808a2,librawpointer-f73a58cd128df828,libnum_rational-527bb4af2a8273af,libnum_integer-eaf56f037f44b96c,libtypenum-edec2471d71e3ff6,libsimba-34e173d5bf61ed5c,libwide-fca37db65854cccb,libsafe_arch-1f8c55e704099ca9,libbytemuck-d64d7e9744cd12ae,libnum_complex-2158d2ce6fbab3b8,librand-7a4aa9d1fdcac6b4,librand_chacha-6a9818b75bb1279b,libppv_lite86-9f3414099d5801d8,librand_core-3554dbca1744bf65,libgetrandom-b51fc064ca144789,libbincode-f7697e5c8a3725db,libserde-7d338d6d62bbd6c1,liblog-17d4c04744091b72,libitertools-1910558703caedba,libpyo3-70fc57b7bf2c34f6,libmemoffset-a5a240ae285dd09a,libonce_cell-18f4b407e28e12b6,libpyo3_ffi-e49b8b2c50bfd98a,liblibc-f5c905995cce61d3,libunindent-a660ddbcf1396680,libextsort-d4e00f56949d17fa,libtempfile-33b3cc82cd8a8f5f,libfastrand-8176d9923c123d38,librustix-c831f801e7d2a5d8,libbitflags-e2ae9f1de5f0445f,liblinux_raw_sys-56cc622a5bb02e92,libcfg_if-3183e62f61f23a61,librayon-937ea05ec8e0296c,librayon_core-621f7bd31e10fa17,libcrossbeam_deque-f2c3fd5e7bbfd927,libcrossbeam_epoch-ed4a2d3daceac61a,libcrossbeam_utils-70904e6a5a5294cc,libeither-e3ab338dd559fca0,libapprox-9ca7c1181f1a7a2b,libnum_traits-cfc634d4f0a04bcf}.rlib" "/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libstd-*,libpanic_unwind-*,libobject-*,libmemchr-*,libaddr2line-*,libgimli-*,librustc_demangle-*,libstd_detect-*,libhashbrown-*,librustc_std_workspace_alloc-*,libminiz_oxide-*,libadler2-*,libunwind-*,libcfg_if-*,liblibc-*,librustc_std_workspace_core-*,liballoc-*,libcore-*,libcompiler_builtins-*}.rlib" "-Wl,-Bdynamic" "-lgcc_s" "-lutil" "-lrt" "-lpthread" "-lm" "-ldl" "-lc" "-L" "/tmp/rustcyEDj04/raw-dylibs" "-B/lib/rustlib/x86_64-unknown-linux-gnu/bin/gcc-ld" "-fuse-ld=lld" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/opt/rustwide/target/debug/deps/spearman-a2842b653e95d823" "-Wl,--gc-sections" "-pie" "-Wl,-z,relro,-z,now" "-nodefaultlibs" [INFO] [stdout] = note: some arguments are omitted. use `--verbose` to show all linker arguments [INFO] [stdout] = note: rust-lld: error: undefined symbol: PyExc_Exception [INFO] [stdout] >>> referenced by exceptions.rs:309 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-0.22.2/src/exceptions.rs:309) [INFO] [stdout] >>> ggca.ggca.175a4e69c89838ca-cgu.14.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::had7df04b87b7cbfd) in archive /opt/rustwide/target/debug/deps/libggca.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-0.22.2/src/exceptions.rs:309) [INFO] [stdout] >>> ggca.ggca.175a4e69c89838ca-cgu.14.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::had7df04b87b7cbfd) in archive /opt/rustwide/target/debug/deps/libggca.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: _Py_Dealloc [INFO] [stdout] >>> referenced by object.rs:611 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-ffi-0.22.2/src/object.rs:611) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h2f26f0aed5f89c8f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by object.rs:611 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-ffi-0.22.2/src/object.rs:611) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h88b27dc260f2fdea) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by object.rs:611 (/opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/pyo3-ffi-0.22.2/src/object.rs:611) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::hc2ba13d66f24e9d9) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced 4 more times [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyObject_Repr [INFO] [stdout] >>> referenced by any.rs:2277 (src/types/any.rs:2277) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::repr::h865265723feadc58) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyObject_Str [INFO] [stdout] >>> referenced by any.rs:2285 (src/types/any.rs:2285) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::str::h067d209e07a13158) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyBytes_AsString [INFO] [stdout] >>> referenced by bytes.rs:193 (src/types/bytes.rs:193) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::h64ed8ded3b8d215f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyBytes_Size [INFO] [stdout] >>> referenced by bytes.rs:194 (src/types/bytes.rs:194) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::h64ed8ded3b8d215f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyUnicode_AsUTF8AndSize [INFO] [stdout] >>> referenced by string.rs:377 (src/types/string.rs:377) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_str::hce5e462692297a9b) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyUnicode_AsEncodedString [INFO] [stdout] >>> referenced by string.rs:416 (src/types/string.rs:416) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_string_lossy::hed82ab9bac7b4577) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyType_GetName [INFO] [stdout] >>> referenced by typeobject.rs:178 (src/types/typeobject.rs:178) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..typeobject..PyType$GT$$u20$as$u20$pyo3..types..typeobject..PyTypeMethods$GT$::name::h378f94ec16f40d0f) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyException_GetTraceback [INFO] [stdout] >>> referenced by err_state.rs:40 (src/err/err_state.rs:40) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::ptraceback::h725db2326fc77320) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_GetRaisedException [INFO] [stdout] >>> referenced by err_state.rs:48 (src/err/err_state.rs:48) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::take::h19b68f67ee6b7fd8) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_SetRaisedException [INFO] [stdout] >>> referenced by err_state.rs:206 (src/err/err_state.rs:206) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::PyErrState::restore::haca2fc16063856f8) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_SetString [INFO] [stdout] >>> referenced by err_state.rs:241 (src/err/err_state.rs:241) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::raise_lazy::h150c8edc64a09730) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyErr_SetObject [INFO] [stdout] >>> referenced by err_state.rs:246 (src/err/err_state.rs:246) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::err::err_state::raise_lazy::h150c8edc64a09730) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyUnicode_FromStringAndSize [INFO] [stdout] >>> referenced by string.rs:167 (src/types/string.rs:167) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(pyo3::types::string::PyString::new_bound::h1be2383f65fc2099) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_BaseException [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h1b6d319a7bbd627c) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h1b6d319a7bbd627c) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_OSError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hfd190deee279e0be) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hfd190deee279e0be) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_TypeError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h7ccbebe3eaea6402) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h7ccbebe3eaea6402) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_BlockingIOError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::he9438d8bf38e89ac) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::he9438d8bf38e89ac) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: undefined symbol: PyExc_BrokenPipeError [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBrokenPipeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h01b488966619cdd2) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-70fc57b7bf2c34f6.pyo3.20841cbe59ec78c4-cgu.08.rcgu.o:(_$LT$pyo3..exceptions..PyBrokenPipeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h01b488966619cdd2) in archive /opt/rustwide/target/debug/deps/libpyo3-70fc57b7bf2c34f6.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: too many errors emitted, stopping now (use --error-limit=0 to see all errors) [INFO] [stdout] collect2: error: ld returned 1 exit status [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `ggca` (test "spearman") due to 1 previous error [INFO] [stderr] error: could not compile `ggca` (test "kendall") due to 1 previous error [INFO] running `Command { std: "docker" "inspect" "2447d7bc4450c7dc23079f0418efb380198191049128c3b0495891bb7b55854e", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "2447d7bc4450c7dc23079f0418efb380198191049128c3b0495891bb7b55854e", kill_on_drop: false }` [INFO] [stdout] 2447d7bc4450c7dc23079f0418efb380198191049128c3b0495891bb7b55854e