[INFO] fetching crate ggca 1.0.0...
[INFO] testing ggca-1.0.0 against beta-2025-09-21 for beta-1.91-3
[INFO] extracting crate ggca 1.0.0 into /workspace/builds/worker-5-tc2/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-tc2/source/Cargo.toml
[INFO] validating manifest of crates.io crate ggca 1.0.0 on toolchain beta-2025-09-21
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+beta-2025-09-21" "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" "+beta-2025-09-21" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2025-09-21" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] b67e79a7b8a5970ba0f618835d28d6322a35491eba3676b675e775b39a5af12a
[INFO] running `Command { std: "docker" "start" "-a" "b67e79a7b8a5970ba0f618835d28d6322a35491eba3676b675e775b39a5af12a", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "b67e79a7b8a5970ba0f618835d28d6322a35491eba3676b675e775b39a5af12a", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "b67e79a7b8a5970ba0f618835d28d6322a35491eba3676b675e775b39a5af12a", kill_on_drop: false }`
[INFO] [stdout] b67e79a7b8a5970ba0f618835d28d6322a35491eba3676b675e775b39a5af12a
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=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" "+beta-2025-09-21" "build" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] cf5573dbafaee170126f3f3854f707e9d7723e2326a2ac8e067ff9679fd7e17a
[INFO] running `Command { std: "docker" "start" "-a" "cf5573dbafaee170126f3f3854f707e9d7723e2326a2ac8e067ff9679fd7e17a", 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 serde_json v1.0.120
[INFO] [stderr]    Compiling crossbeam-utils v0.8.20
[INFO] [stderr]    Compiling rustix v0.38.34
[INFO] [stderr]    Compiling bitflags v2.6.0
[INFO] [stderr]    Compiling camino v1.1.7
[INFO] [stderr]    Compiling unicase v2.7.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 bytemuck v1.16.1
[INFO] [stderr]    Compiling same-file v1.0.6
[INFO] [stderr]    Compiling fastrand v2.1.0
[INFO] [stderr]    Compiling ppv-lite86 v0.2.17
[INFO] [stderr]    Compiling walkdir v2.5.0
[INFO] [stderr]    Compiling safe_arch v0.7.2
[INFO] [stderr]    Compiling bytecount v0.6.8
[INFO] [stderr]    Compiling glob v0.3.1
[INFO] [stderr]    Compiling aho-corasick v1.1.3
[INFO] [stderr]    Compiling syn v2.0.70
[INFO] [stderr]    Compiling either v1.13.0
[INFO] [stderr]    Compiling rawpointer v0.2.1
[INFO] [stderr]    Compiling num-traits v0.2.19
[INFO] [stderr]    Compiling matrixmultiply v0.3.8
[INFO] [stderr]    Compiling crossbeam-epoch v0.9.18
[INFO] [stderr]    Compiling memoffset v0.9.1
[INFO] [stderr]    Compiling regex-syntax v0.8.4
[INFO] [stderr]    Compiling pyo3-build-config v0.22.2
[INFO] [stderr]    Compiling csv-core v0.1.11
[INFO] [stderr]    Compiling wide v0.7.25
[INFO] [stderr]    Compiling termcolor v1.4.1
[INFO] [stderr]    Compiling indoc v2.0.5
[INFO] [stderr]    Compiling log v0.4.22
[INFO] [stderr]    Compiling unindent v0.2.3
[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 num-complex v0.4.6
[INFO] [stderr]    Compiling num-integer v0.1.46
[INFO] [stderr]    Compiling approx v0.5.1
[INFO] [stderr]    Compiling rayon v1.10.0
[INFO] [stderr]    Compiling getrandom v0.2.15
[INFO] [stderr]    Compiling atty v0.2.14
[INFO] [stderr]    Compiling regex-automata v0.4.7
[INFO] [stderr]    Compiling rand_core v0.6.4
[INFO] [stderr]    Compiling num-rational v0.4.2
[INFO] [stderr]    Compiling rand_chacha v0.3.1
[INFO] [stderr]    Compiling rand v0.8.5
[INFO] [stderr]    Compiling pyo3-ffi v0.22.2
[INFO] [stderr]    Compiling pyo3-macros-backend v0.22.2
[INFO] [stderr]    Compiling pyo3 v0.22.2
[INFO] [stderr]    Compiling tempfile v3.10.1
[INFO] [stderr]    Compiling simba v0.8.1
[INFO] [stderr]    Compiling rand_distr v0.4.3
[INFO] [stderr]    Compiling regex v1.10.5
[INFO] [stderr]    Compiling serde_derive v1.0.204
[INFO] [stderr]    Compiling nalgebra-macros v0.2.2
[INFO] [stderr]    Compiling env_logger v0.9.3
[INFO] [stderr]    Compiling pyo3-macros v0.22.2
[INFO] [stderr]    Compiling nalgebra v0.32.6
[INFO] [stderr]    Compiling cargo-platform v0.1.8
[INFO] [stderr]    Compiling bincode v1.3.3
[INFO] [stderr]    Compiling csv v1.3.0
[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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 46.58s
[INFO] running `Command { std: "docker" "inspect" "cf5573dbafaee170126f3f3854f707e9d7723e2326a2ac8e067ff9679fd7e17a", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "cf5573dbafaee170126f3f3854f707e9d7723e2326a2ac8e067ff9679fd7e17a", kill_on_drop: false }`
[INFO] [stdout] cf5573dbafaee170126f3f3854f707e9d7723e2326a2ac8e067ff9679fd7e17a
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=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" "+beta-2025-09-21" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] b6b2fefeb728f762cf621b618a5102b42e96feb90c35e11ee9a6ac860518bc5c
[INFO] running `Command { std: "docker" "start" "-a" "b6b2fefeb728f762cf621b618a5102b42e96feb90c35e11ee9a6ac860518bc5c", kill_on_drop: false }`
[INFO] [stderr]    Compiling serde_json v1.0.120
[INFO] [stderr]    Compiling half v2.4.1
[INFO] [stderr]    Compiling plotters-backend v0.3.6
[INFO] [stderr]    Compiling ciborium-io v0.2.2
[INFO] [stderr]    Compiling clap_lex v0.7.1
[INFO] [stderr]    Compiling anstyle v1.0.7
[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 plotters v0.3.6
[INFO] [stderr]    Compiling clap_builder v4.5.9
[INFO] [stderr]    Compiling ciborium-ll v0.2.2
[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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/rustc8xsSbA/symbols.o" "<2 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "/opt/rustwide/target/debug/deps/{libggca,libfast_float-615efa375346931c,libenv_logger-6768c135ead1d474,libatty-391c878188a805f6,libtermcolor-cbafc8825e041b3d,libhumantime-9f900d7885b5087e,libregex-b3036468f81da3c3,libregex_automata-105e8535a042310a,libaho_corasick-847080ddcc800a8c,libregex_syntax-b34d0d3f3a197100,libcsv-a4093e49945fb48b,libryu-a980823ac8640001,libitoa-20e94f961f8d160c,libcsv_core-d6ac3c63368d6ac7,libmemchr-08f38e9718637002,libstatrs-7acc1a5f037176e6,libnalgebra-be524c155033124d,librand_distr-2469a3389f497574,libmatrixmultiply-28a888e6c99beb11,librawpointer-10d892ea69c462d6,libnum_rational-8574d91c643bae41,libnum_integer-92829029e93b3980,libtypenum-1862a5dd6fcdc44c,libsimba-0cff735aacb2e553,libwide-a3fb9af7b81a9c93,libsafe_arch-5bf50cf7f85c4749,libbytemuck-78027be639f0e0f7,libnum_complex-48641ed065deb522,librand-99565960cf224d6b,librand_chacha-368639fad3a1c605,libppv_lite86-74d192d5fb0d20a2,librand_core-9c0405eeced83bd6,libgetrandom-8b8aac7d6dc2cc9c,libapprox-6392729c42cce874,libnum_traits-cae5556ec797c756,libbincode-20d601ac5080f513,libserde-7e4d81ce70666db4,liblog-368e05ac2c0115e3,libitertools-217b25dfd86c44c6,libpyo3-2045bc840d8b78a7,libmemoffset-797312a586f4d76f,libonce_cell-a1d7742f74efe1da,libpyo3_ffi-65bf35c3ba10ba56,liblibc-81b33709b71653e4,libunindent-ba611b0c58f2b27f,libextsort-2f3433f1f7fd6a22,libtempfile-5eb176ffeba8a342,libfastrand-5e3bec3d1dadb2e4,librustix-83cf1c19c41139d0,libbitflags-c95e5b195a86a9bf,liblinux_raw_sys-07d08e485b51e8af,libcfg_if-3e7fc4e38d4a72b5,librayon-556b83ff68a1cd7e,librayon_core-724bd3cb64d286e7,libcrossbeam_deque-d61e12785107a802,libcrossbeam_epoch-a6cf04f6d42ccc60,libcrossbeam_utils-b6032feb2e6cd592,libeither-b4418dba5a443acb}.rlib" "<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libstd-*,libpanic_unwind-*,libobject-*,libmemchr-*,libaddr2line-*,libgimli-*,libcfg_if-*,librustc_demangle-*,libstd_detect-*,libhashbrown-*,librustc_std_workspace_alloc-*,libminiz_oxide-*,libadler2-*,libunwind-*,liblibc-*,librustc_std_workspace_core-*,liballoc-*,libcore-*,libcompiler_builtins-*}.rlib" "-Wl,-Bdynamic" "-lgcc_s" "-lutil" "-lrt" "-lpthread" "-lm" "-ldl" "-lc" "-L" "/tmp/rustc8xsSbA/raw-dylibs" "-B<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/bin/gcc-ld" "-fuse-ld=lld" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/opt/rustwide/target/debug/examples/cpg_site_ids-eeb98a021edaf46b" "-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.fa8f62c4babe6a57-cgu.06.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4394d038b1214672) 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.fa8f62c4babe6a57-cgu.06.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4394d038b1214672) in archive /opt/rustwide/target/debug/deps/libggca.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::str::h5a0af419fb3dce12) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::repr::h5d160586697e75e8) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..typeobject..PyType$GT$$u20$as$u20$pyo3..types..typeobject..PyTypeMethods$GT$::name::h8dd2334cc7be7432) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::hb5ee8562845ae686) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::hb5ee8562845ae686) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_string_lossy::h438bc087230b6ba9) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_str::h98a01981de1da149) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h33179a2a9510c094) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h6bff559bab9aa613) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h82230c5a0e8fa4f0) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced 4 more times
[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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::err::err_state::PyErrState::restore::h8ba634a8b933ca78) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::err::err_state::raise_lazy::hd4f5ff9e1410a063) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::err::err_state::raise_lazy::hd4f5ff9e1410a063) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::ptraceback::h7b17e25032b5f7fa) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::take::h5cf5d3aa2e7fc4ff) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::types::string::PyString::new_bound::h2689cace97d10846) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h94bf82366b3a2fdb) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h94bf82366b3a2fdb) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hbaff9174febb182a) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hbaff9174febb182a) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           
[INFO] [stdout]           rust-lld: error: undefined symbol: PyExc_TimeoutError
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyTimeoutError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hf64c84a18616a43c) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyTimeoutError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hf64c84a18616a43c) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h82bd90ad606029c6) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h82bd90ad606029c6) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h7ce6f0917406de35) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h7ce6f0917406de35) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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/rustcwABQbX/symbols.o" "<2 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libtest-*,libgetopts-*,librustc_std_workspace_std-*}.rlib" "/opt/rustwide/target/debug/deps/{libggca,libfast_float-615efa375346931c,libenv_logger-6768c135ead1d474,libatty-391c878188a805f6,libtermcolor-cbafc8825e041b3d,libhumantime-9f900d7885b5087e,libregex-b3036468f81da3c3,libregex_automata-105e8535a042310a,libaho_corasick-847080ddcc800a8c,libregex_syntax-b34d0d3f3a197100,libcsv-a4093e49945fb48b,libryu-a980823ac8640001,libitoa-20e94f961f8d160c,libcsv_core-d6ac3c63368d6ac7,libmemchr-08f38e9718637002,libstatrs-7acc1a5f037176e6,libnalgebra-be524c155033124d,librand_distr-2469a3389f497574,libmatrixmultiply-28a888e6c99beb11,librawpointer-10d892ea69c462d6,libnum_rational-8574d91c643bae41,libnum_integer-92829029e93b3980,libtypenum-1862a5dd6fcdc44c,libsimba-0cff735aacb2e553,libwide-a3fb9af7b81a9c93,libsafe_arch-5bf50cf7f85c4749,libbytemuck-78027be639f0e0f7,libnum_complex-48641ed065deb522,librand-99565960cf224d6b,librand_chacha-368639fad3a1c605,libppv_lite86-74d192d5fb0d20a2,librand_core-9c0405eeced83bd6,libgetrandom-8b8aac7d6dc2cc9c,libbincode-20d601ac5080f513,libserde-7e4d81ce70666db4,liblog-368e05ac2c0115e3,libitertools-217b25dfd86c44c6,libpyo3-2045bc840d8b78a7,libmemoffset-797312a586f4d76f,libonce_cell-a1d7742f74efe1da,libpyo3_ffi-65bf35c3ba10ba56,liblibc-81b33709b71653e4,libunindent-ba611b0c58f2b27f,libextsort-2f3433f1f7fd6a22,libtempfile-5eb176ffeba8a342,libfastrand-5e3bec3d1dadb2e4,librustix-83cf1c19c41139d0,libbitflags-c95e5b195a86a9bf,liblinux_raw_sys-07d08e485b51e8af,libcfg_if-3e7fc4e38d4a72b5,librayon-556b83ff68a1cd7e,librayon_core-724bd3cb64d286e7,libcrossbeam_deque-d61e12785107a802,libcrossbeam_epoch-a6cf04f6d42ccc60,libcrossbeam_utils-b6032feb2e6cd592,libeither-b4418dba5a443acb,libapprox-6392729c42cce874,libnum_traits-cae5556ec797c756}.rlib" "<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libstd-*,libpanic_unwind-*,libobject-*,libmemchr-*,libaddr2line-*,libgimli-*,libcfg_if-*,librustc_demangle-*,libstd_detect-*,libhashbrown-*,librustc_std_workspace_alloc-*,libminiz_oxide-*,libadler2-*,libunwind-*,liblibc-*,librustc_std_workspace_core-*,liballoc-*,libcore-*,libcompiler_builtins-*}.rlib" "-Wl,-Bdynamic" "-lgcc_s" "-lutil" "-lrt" "-lpthread" "-lm" "-ldl" "-lc" "-L" "/tmp/rustcwABQbX/raw-dylibs" "-B<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/bin/gcc-ld" "-fuse-ld=lld" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/opt/rustwide/target/debug/deps/nan_filtering-121e10eb75a58e2b" "-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.fa8f62c4babe6a57-cgu.06.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4394d038b1214672) 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.fa8f62c4babe6a57-cgu.06.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4394d038b1214672) in archive /opt/rustwide/target/debug/deps/libggca.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::str::h5a0af419fb3dce12) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::repr::h5d160586697e75e8) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..typeobject..PyType$GT$$u20$as$u20$pyo3..types..typeobject..PyTypeMethods$GT$::name::h8dd2334cc7be7432) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::hb5ee8562845ae686) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::hb5ee8562845ae686) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_string_lossy::h438bc087230b6ba9) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_str::h98a01981de1da149) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h33179a2a9510c094) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h6bff559bab9aa613) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h82230c5a0e8fa4f0) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced 4 more times
[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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.10.rcgu.o:(pyo3::err::panic_after_error::h11fa61957aaba15c) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.10.rcgu.o:(pyo3::err::PyErr::new_type_bound::h875e93204a2e6129) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.10.rcgu.o:(pyo3::err::PyErr::print_panic_and_unwind::h96224d876c13f05e) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.10.rcgu.o:(pyo3::err::PyErr::write_unraisable_bound::h5cd62dcd4a3327a9) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.11.rcgu.o:(pyo3::gil::prepare_freethreaded_python::_$u7b$$u7b$closure$u7d$$u7d$::h6d87348cba17de63) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by gil.rs:199 (src/gil.rs:199)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.11.rcgu.o:(pyo3::gil::GILGuard::acquire::_$u7b$$u7b$closure$u7d$$u7d$::h7bc404b40c30cf18) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.11.rcgu.o:(pyo3::gil::prepare_freethreaded_python::_$u7b$$u7b$closure$u7d$$u7d$::h6d87348cba17de63) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.11.rcgu.o:(pyo3::gil::prepare_freethreaded_python::_$u7b$$u7b$closure$u7d$$u7d$::h6d87348cba17de63) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.11.rcgu.o:(pyo3::gil::GILGuard::acquire_unchecked::h427772b4a6fb96d2) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.11.rcgu.o:(_$LT$pyo3..gil..GILGuard$u20$as$u20$core..ops..drop..Drop$GT$::drop::hdfc90bc8f81323f1) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::err::err_state::PyErrState::restore::h8ba634a8b933ca78) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::err::err_state::raise_lazy::hd4f5ff9e1410a063) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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/rustcAsXQoj/symbols.o" "<2 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libtest-*,libgetopts-*,librustc_std_workspace_std-*}.rlib" "/opt/rustwide/target/debug/deps/{liblazy_static-3674be3f4245d19b,libggca,libfast_float-615efa375346931c,libenv_logger-6768c135ead1d474,libatty-391c878188a805f6,libtermcolor-cbafc8825e041b3d,libhumantime-9f900d7885b5087e,libregex-b3036468f81da3c3,libregex_automata-105e8535a042310a,libaho_corasick-847080ddcc800a8c,libregex_syntax-b34d0d3f3a197100,libcsv-a4093e49945fb48b,libryu-a980823ac8640001,libitoa-20e94f961f8d160c,libcsv_core-d6ac3c63368d6ac7,libmemchr-08f38e9718637002,libstatrs-7acc1a5f037176e6,libnalgebra-be524c155033124d,librand_distr-2469a3389f497574,libmatrixmultiply-28a888e6c99beb11,librawpointer-10d892ea69c462d6,libnum_rational-8574d91c643bae41,libnum_integer-92829029e93b3980,libtypenum-1862a5dd6fcdc44c,libsimba-0cff735aacb2e553,libwide-a3fb9af7b81a9c93,libsafe_arch-5bf50cf7f85c4749,libbytemuck-78027be639f0e0f7,libnum_complex-48641ed065deb522,librand-99565960cf224d6b,librand_chacha-368639fad3a1c605,libppv_lite86-74d192d5fb0d20a2,librand_core-9c0405eeced83bd6,libgetrandom-8b8aac7d6dc2cc9c,libbincode-20d601ac5080f513,libserde-7e4d81ce70666db4,liblog-368e05ac2c0115e3,libitertools-217b25dfd86c44c6,libpyo3-2045bc840d8b78a7,libmemoffset-797312a586f4d76f,libonce_cell-a1d7742f74efe1da,libpyo3_ffi-65bf35c3ba10ba56,liblibc-81b33709b71653e4,libunindent-ba611b0c58f2b27f,libextsort-2f3433f1f7fd6a22,libtempfile-5eb176ffeba8a342,libfastrand-5e3bec3d1dadb2e4,librustix-83cf1c19c41139d0,libbitflags-c95e5b195a86a9bf,liblinux_raw_sys-07d08e485b51e8af,libcfg_if-3e7fc4e38d4a72b5,librayon-556b83ff68a1cd7e,librayon_core-724bd3cb64d286e7,libcrossbeam_deque-d61e12785107a802,libcrossbeam_epoch-a6cf04f6d42ccc60,libcrossbeam_utils-b6032feb2e6cd592,libeither-b4418dba5a443acb,libapprox-6392729c42cce874,libnum_traits-cae5556ec797c756}.rlib" "<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libstd-*,libpanic_unwind-*,libobject-*,libmemchr-*,libaddr2line-*,libgimli-*,libcfg_if-*,librustc_demangle-*,libstd_detect-*,libhashbrown-*,librustc_std_workspace_alloc-*,libminiz_oxide-*,libadler2-*,libunwind-*,liblibc-*,librustc_std_workspace_core-*,liballoc-*,libcore-*,libcompiler_builtins-*}.rlib" "-Wl,-Bdynamic" "-lgcc_s" "-lutil" "-lrt" "-lpthread" "-lm" "-ldl" "-lc" "-L" "/tmp/rustcAsXQoj/raw-dylibs" "-B<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/bin/gcc-ld" "-fuse-ld=lld" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/opt/rustwide/target/debug/deps/cpg_site_ids-f34762558481194d" "-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.fa8f62c4babe6a57-cgu.06.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4394d038b1214672) 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.fa8f62c4babe6a57-cgu.06.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4394d038b1214672) in archive /opt/rustwide/target/debug/deps/libggca.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::str::h5a0af419fb3dce12) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::repr::h5d160586697e75e8) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..typeobject..PyType$GT$$u20$as$u20$pyo3..types..typeobject..PyTypeMethods$GT$::name::h8dd2334cc7be7432) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::hb5ee8562845ae686) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::hb5ee8562845ae686) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_string_lossy::h438bc087230b6ba9) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_str::h98a01981de1da149) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h33179a2a9510c094) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h6bff559bab9aa613) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h82230c5a0e8fa4f0) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced 4 more times
[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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.11.rcgu.o:(pyo3::gil::prepare_freethreaded_python::_$u7b$$u7b$closure$u7d$$u7d$::h6d87348cba17de63) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by gil.rs:199 (src/gil.rs:199)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.11.rcgu.o:(pyo3::gil::GILGuard::acquire::_$u7b$$u7b$closure$u7d$$u7d$::h7bc404b40c30cf18) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.11.rcgu.o:(pyo3::gil::prepare_freethreaded_python::_$u7b$$u7b$closure$u7d$$u7d$::h6d87348cba17de63) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.11.rcgu.o:(pyo3::gil::prepare_freethreaded_python::_$u7b$$u7b$closure$u7d$$u7d$::h6d87348cba17de63) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.11.rcgu.o:(pyo3::gil::GILGuard::acquire_unchecked::h427772b4a6fb96d2) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.11.rcgu.o:(_$LT$pyo3..gil..GILGuard$u20$as$u20$core..ops..drop..Drop$GT$::drop::hdfc90bc8f81323f1) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.10.rcgu.o:(pyo3::err::panic_after_error::h11fa61957aaba15c) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.10.rcgu.o:(pyo3::err::PyErr::new_type_bound::h875e93204a2e6129) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.10.rcgu.o:(pyo3::err::PyErr::print_panic_and_unwind::h96224d876c13f05e) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.10.rcgu.o:(pyo3::err::PyErr::write_unraisable_bound::h5cd62dcd4a3327a9) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::err::err_state::PyErrState::restore::h8ba634a8b933ca78) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::err::err_state::raise_lazy::hd4f5ff9e1410a063) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stderr] error: could not compile `ggca` (example "cpg_site_ids") due to 1 previous error
[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/rustcyqRZ72/symbols.o" "<2 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "/opt/rustwide/target/debug/deps/{libggca,libfast_float-615efa375346931c,libenv_logger-6768c135ead1d474,libatty-391c878188a805f6,libtermcolor-cbafc8825e041b3d,libhumantime-9f900d7885b5087e,libregex-b3036468f81da3c3,libregex_automata-105e8535a042310a,libaho_corasick-847080ddcc800a8c,libregex_syntax-b34d0d3f3a197100,libcsv-a4093e49945fb48b,libryu-a980823ac8640001,libitoa-20e94f961f8d160c,libcsv_core-d6ac3c63368d6ac7,libmemchr-08f38e9718637002,libstatrs-7acc1a5f037176e6,libnalgebra-be524c155033124d,librand_distr-2469a3389f497574,libmatrixmultiply-28a888e6c99beb11,librawpointer-10d892ea69c462d6,libnum_rational-8574d91c643bae41,libnum_integer-92829029e93b3980,libtypenum-1862a5dd6fcdc44c,libsimba-0cff735aacb2e553,libwide-a3fb9af7b81a9c93,libsafe_arch-5bf50cf7f85c4749,libbytemuck-78027be639f0e0f7,libnum_complex-48641ed065deb522,librand-99565960cf224d6b,librand_chacha-368639fad3a1c605,libppv_lite86-74d192d5fb0d20a2,librand_core-9c0405eeced83bd6,libgetrandom-8b8aac7d6dc2cc9c,libapprox-6392729c42cce874,libnum_traits-cae5556ec797c756,libbincode-20d601ac5080f513,libserde-7e4d81ce70666db4,liblog-368e05ac2c0115e3,libitertools-217b25dfd86c44c6,libpyo3-2045bc840d8b78a7,libmemoffset-797312a586f4d76f,libonce_cell-a1d7742f74efe1da,libpyo3_ffi-65bf35c3ba10ba56,liblibc-81b33709b71653e4,libunindent-ba611b0c58f2b27f,libextsort-2f3433f1f7fd6a22,libtempfile-5eb176ffeba8a342,libfastrand-5e3bec3d1dadb2e4,librustix-83cf1c19c41139d0,libbitflags-c95e5b195a86a9bf,liblinux_raw_sys-07d08e485b51e8af,libcfg_if-3e7fc4e38d4a72b5,librayon-556b83ff68a1cd7e,librayon_core-724bd3cb64d286e7,libcrossbeam_deque-d61e12785107a802,libcrossbeam_epoch-a6cf04f6d42ccc60,libcrossbeam_utils-b6032feb2e6cd592,libeither-b4418dba5a443acb}.rlib" "<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libstd-*,libpanic_unwind-*,libobject-*,libmemchr-*,libaddr2line-*,libgimli-*,libcfg_if-*,librustc_demangle-*,libstd_detect-*,libhashbrown-*,librustc_std_workspace_alloc-*,libminiz_oxide-*,libadler2-*,libunwind-*,liblibc-*,librustc_std_workspace_core-*,liballoc-*,libcore-*,libcompiler_builtins-*}.rlib" "-Wl,-Bdynamic" "-lgcc_s" "-lutil" "-lrt" "-lpthread" "-lm" "-ldl" "-lc" "-L" "/tmp/rustcyqRZ72/raw-dylibs" "-B<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/bin/gcc-ld" "-fuse-ld=lld" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/opt/rustwide/target/debug/examples/basic-47d61be78addaafe" "-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.fa8f62c4babe6a57-cgu.06.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4394d038b1214672) 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.fa8f62c4babe6a57-cgu.06.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4394d038b1214672) in archive /opt/rustwide/target/debug/deps/libggca.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::str::h5a0af419fb3dce12) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::repr::h5d160586697e75e8) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..typeobject..PyType$GT$$u20$as$u20$pyo3..types..typeobject..PyTypeMethods$GT$::name::h8dd2334cc7be7432) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::hb5ee8562845ae686) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::hb5ee8562845ae686) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_string_lossy::h438bc087230b6ba9) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_str::h98a01981de1da149) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h33179a2a9510c094) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h6bff559bab9aa613) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h82230c5a0e8fa4f0) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced 4 more times
[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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.10.rcgu.o:(pyo3::err::panic_after_error::h11fa61957aaba15c) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.10.rcgu.o:(pyo3::err::PyErr::new_type_bound::h875e93204a2e6129) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.10.rcgu.o:(pyo3::err::PyErr::print_panic_and_unwind::h96224d876c13f05e) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.10.rcgu.o:(pyo3::err::PyErr::write_unraisable_bound::h5cd62dcd4a3327a9) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.11.rcgu.o:(pyo3::gil::prepare_freethreaded_python::_$u7b$$u7b$closure$u7d$$u7d$::h6d87348cba17de63) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by gil.rs:199 (src/gil.rs:199)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.11.rcgu.o:(pyo3::gil::GILGuard::acquire::_$u7b$$u7b$closure$u7d$$u7d$::h7bc404b40c30cf18) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.11.rcgu.o:(pyo3::gil::prepare_freethreaded_python::_$u7b$$u7b$closure$u7d$$u7d$::h6d87348cba17de63) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.11.rcgu.o:(pyo3::gil::prepare_freethreaded_python::_$u7b$$u7b$closure$u7d$$u7d$::h6d87348cba17de63) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.11.rcgu.o:(pyo3::gil::GILGuard::acquire_unchecked::h427772b4a6fb96d2) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.11.rcgu.o:(_$LT$pyo3..gil..GILGuard$u20$as$u20$core..ops..drop..Drop$GT$::drop::hdfc90bc8f81323f1) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::err::err_state::PyErrState::restore::h8ba634a8b933ca78) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::err::err_state::raise_lazy::hd4f5ff9e1410a063) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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] [stdout] error: linking with `cc` failed: exit status: 1
[INFO] [stdout]   |
[INFO] [stdout]   = note:  "cc" "-m64" "/tmp/rustcJLQRtW/symbols.o" "<5 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libtest-*,libgetopts-*,librustc_std_workspace_std-*}.rlib" "/opt/rustwide/target/debug/deps/{liblazy_static-3674be3f4245d19b,libggca,libfast_float-615efa375346931c,libenv_logger-6768c135ead1d474,libatty-391c878188a805f6,libtermcolor-cbafc8825e041b3d,libhumantime-9f900d7885b5087e,libregex-b3036468f81da3c3,libregex_automata-105e8535a042310a,libaho_corasick-847080ddcc800a8c,libregex_syntax-b34d0d3f3a197100,libcsv-a4093e49945fb48b,libryu-a980823ac8640001,libitoa-20e94f961f8d160c,libcsv_core-d6ac3c63368d6ac7,libmemchr-08f38e9718637002,libstatrs-7acc1a5f037176e6,libnalgebra-be524c155033124d,librand_distr-2469a3389f497574,libmatrixmultiply-28a888e6c99beb11,librawpointer-10d892ea69c462d6,libnum_rational-8574d91c643bae41,libnum_integer-92829029e93b3980,libtypenum-1862a5dd6fcdc44c,libsimba-0cff735aacb2e553,libwide-a3fb9af7b81a9c93,libsafe_arch-5bf50cf7f85c4749,libbytemuck-78027be639f0e0f7,libnum_complex-48641ed065deb522,librand-99565960cf224d6b,librand_chacha-368639fad3a1c605,libppv_lite86-74d192d5fb0d20a2,librand_core-9c0405eeced83bd6,libgetrandom-8b8aac7d6dc2cc9c,libbincode-20d601ac5080f513,libserde-7e4d81ce70666db4,liblog-368e05ac2c0115e3,libitertools-217b25dfd86c44c6,libpyo3-2045bc840d8b78a7,libmemoffset-797312a586f4d76f,libonce_cell-a1d7742f74efe1da,libpyo3_ffi-65bf35c3ba10ba56,liblibc-81b33709b71653e4,libunindent-ba611b0c58f2b27f,libextsort-2f3433f1f7fd6a22,libtempfile-5eb176ffeba8a342,libfastrand-5e3bec3d1dadb2e4,librustix-83cf1c19c41139d0,libbitflags-c95e5b195a86a9bf,liblinux_raw_sys-07d08e485b51e8af,libcfg_if-3e7fc4e38d4a72b5,librayon-556b83ff68a1cd7e,librayon_core-724bd3cb64d286e7,libcrossbeam_deque-d61e12785107a802,libcrossbeam_epoch-a6cf04f6d42ccc60,libcrossbeam_utils-b6032feb2e6cd592,libeither-b4418dba5a443acb,libapprox-6392729c42cce874,libnum_traits-cae5556ec797c756}.rlib" "<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libstd-*,libpanic_unwind-*,libobject-*,libmemchr-*,libaddr2line-*,libgimli-*,libcfg_if-*,librustc_demangle-*,libstd_detect-*,libhashbrown-*,librustc_std_workspace_alloc-*,libminiz_oxide-*,libadler2-*,libunwind-*,liblibc-*,librustc_std_workspace_core-*,liballoc-*,libcore-*,libcompiler_builtins-*}.rlib" "-Wl,-Bdynamic" "-lgcc_s" "-lutil" "-lrt" "-lpthread" "-lm" "-ldl" "-lc" "-L" "/tmp/rustcJLQRtW/raw-dylibs" "-B<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/bin/gcc-ld" "-fuse-ld=lld" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/opt/rustwide/target/debug/deps/spearman-974dad251f3214e4" "-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.fa8f62c4babe6a57-cgu.06.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4394d038b1214672) 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.fa8f62c4babe6a57-cgu.06.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4394d038b1214672) in archive /opt/rustwide/target/debug/deps/libggca.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::err::err_state::PyErrState::restore::h8ba634a8b933ca78) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::err::err_state::raise_lazy::hd4f5ff9e1410a063) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::err::err_state::raise_lazy::hd4f5ff9e1410a063) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::ptraceback::h7b17e25032b5f7fa) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::take::h5cf5d3aa2e7fc4ff) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::types::string::PyString::new_bound::h2689cace97d10846) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h94bf82366b3a2fdb) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h94bf82366b3a2fdb) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hbaff9174febb182a) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hbaff9174febb182a) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           
[INFO] [stdout]           rust-lld: error: undefined symbol: PyExc_TimeoutError
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyTimeoutError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hf64c84a18616a43c) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyTimeoutError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hf64c84a18616a43c) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h82bd90ad606029c6) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h82bd90ad606029c6) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h7ce6f0917406de35) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h7ce6f0917406de35) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyBrokenPipeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h7237c2ca6f6c40f4) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyBrokenPipeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h7237c2ca6f6c40f4) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           
[INFO] [stdout]           rust-lld: error: undefined symbol: PyExc_FileExistsError
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyFileExistsError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h5d8fb02dc998a902) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyFileExistsError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h5d8fb02dc998a902) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           
[INFO] [stdout]           rust-lld: error: undefined symbol: PyExc_PermissionError
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyPermissionError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hce3979c4f3cffd84) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyPermissionError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hce3979c4f3cffd84) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           
[INFO] [stdout]           rust-lld: error: undefined symbol: PyExc_InterruptedError
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyInterruptedError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4a50de1ba9308c6d) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyInterruptedError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4a50de1ba9308c6d) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           
[INFO] [stdout]           rust-lld: error: undefined symbol: PyExc_FileNotFoundError
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyFileNotFoundError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h79b41d7ab4b552ec) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyFileNotFoundError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h79b41d7ab4b552ec) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           
[INFO] [stdout]           rust-lld: error: undefined symbol: PyExc_ConnectionResetError
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyConnectionResetError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h6f8b87331e5a29fb) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyConnectionResetError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h6f8b87331e5a29fb) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           
[INFO] [stdout]           rust-lld: error: undefined symbol: PyExc_ConnectionAbortedError
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyConnectionAbortedError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h293fc7419d0e1030) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyConnectionAbortedError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h293fc7419d0e1030) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           
[INFO] [stdout]           rust-lld: error: undefined symbol: PyExc_ConnectionRefusedError
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyConnectionRefusedError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h72a266a9611a4350) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyConnectionRefusedError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h72a266a9611a4350) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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] [stdout] error: linking with `cc` failed: exit status: 1
[INFO] [stdout]   |
[INFO] [stdout]   = note:  "cc" "-m64" "/tmp/rustc2MFhKt/symbols.o" "<4 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libtest-*,libgetopts-*,librustc_std_workspace_std-*}.rlib" "/opt/rustwide/target/debug/deps/{liblazy_static-3674be3f4245d19b,libggca,libfast_float-615efa375346931c,libenv_logger-6768c135ead1d474,libatty-391c878188a805f6,libtermcolor-cbafc8825e041b3d,libhumantime-9f900d7885b5087e,libregex-b3036468f81da3c3,libregex_automata-105e8535a042310a,libaho_corasick-847080ddcc800a8c,libregex_syntax-b34d0d3f3a197100,libcsv-a4093e49945fb48b,libryu-a980823ac8640001,libitoa-20e94f961f8d160c,libcsv_core-d6ac3c63368d6ac7,libmemchr-08f38e9718637002,libstatrs-7acc1a5f037176e6,libnalgebra-be524c155033124d,librand_distr-2469a3389f497574,libmatrixmultiply-28a888e6c99beb11,librawpointer-10d892ea69c462d6,libnum_rational-8574d91c643bae41,libnum_integer-92829029e93b3980,libtypenum-1862a5dd6fcdc44c,libsimba-0cff735aacb2e553,libwide-a3fb9af7b81a9c93,libsafe_arch-5bf50cf7f85c4749,libbytemuck-78027be639f0e0f7,libnum_complex-48641ed065deb522,librand-99565960cf224d6b,librand_chacha-368639fad3a1c605,libppv_lite86-74d192d5fb0d20a2,librand_core-9c0405eeced83bd6,libgetrandom-8b8aac7d6dc2cc9c,libbincode-20d601ac5080f513,libserde-7e4d81ce70666db4,liblog-368e05ac2c0115e3,libitertools-217b25dfd86c44c6,libpyo3-2045bc840d8b78a7,libmemoffset-797312a586f4d76f,libonce_cell-a1d7742f74efe1da,libpyo3_ffi-65bf35c3ba10ba56,liblibc-81b33709b71653e4,libunindent-ba611b0c58f2b27f,libextsort-2f3433f1f7fd6a22,libtempfile-5eb176ffeba8a342,libfastrand-5e3bec3d1dadb2e4,librustix-83cf1c19c41139d0,libbitflags-c95e5b195a86a9bf,liblinux_raw_sys-07d08e485b51e8af,libcfg_if-3e7fc4e38d4a72b5,librayon-556b83ff68a1cd7e,librayon_core-724bd3cb64d286e7,libcrossbeam_deque-d61e12785107a802,libcrossbeam_epoch-a6cf04f6d42ccc60,libcrossbeam_utils-b6032feb2e6cd592,libeither-b4418dba5a443acb,libapprox-6392729c42cce874,libnum_traits-cae5556ec797c756}.rlib" "<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libstd-*,libpanic_unwind-*,libobject-*,libmemchr-*,libaddr2line-*,libgimli-*,libcfg_if-*,librustc_demangle-*,libstd_detect-*,libhashbrown-*,librustc_std_workspace_alloc-*,libminiz_oxide-*,libadler2-*,libunwind-*,liblibc-*,librustc_std_workspace_core-*,liballoc-*,libcore-*,libcompiler_builtins-*}.rlib" "-Wl,-Bdynamic" "-lgcc_s" "-lutil" "-lrt" "-lpthread" "-lm" "-ldl" "-lc" "-L" "/tmp/rustc2MFhKt/raw-dylibs" "-B<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/bin/gcc-ld" "-fuse-ld=lld" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/opt/rustwide/target/debug/deps/pearson-de3c7095db5dddd2" "-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.fa8f62c4babe6a57-cgu.06.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4394d038b1214672) 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.fa8f62c4babe6a57-cgu.06.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4394d038b1214672) in archive /opt/rustwide/target/debug/deps/libggca.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::str::h5a0af419fb3dce12) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::repr::h5d160586697e75e8) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..typeobject..PyType$GT$$u20$as$u20$pyo3..types..typeobject..PyTypeMethods$GT$::name::h8dd2334cc7be7432) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::hb5ee8562845ae686) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::hb5ee8562845ae686) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_string_lossy::h438bc087230b6ba9) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_str::h98a01981de1da149) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h33179a2a9510c094) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h6bff559bab9aa613) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h82230c5a0e8fa4f0) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced 4 more times
[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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::err::err_state::PyErrState::restore::h8ba634a8b933ca78) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::err::err_state::raise_lazy::hd4f5ff9e1410a063) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::err::err_state::raise_lazy::hd4f5ff9e1410a063) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::ptraceback::h7b17e25032b5f7fa) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::take::h5cf5d3aa2e7fc4ff) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::types::string::PyString::new_bound::h2689cace97d10846) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h94bf82366b3a2fdb) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h94bf82366b3a2fdb) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hbaff9174febb182a) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hbaff9174febb182a) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           
[INFO] [stdout]           rust-lld: error: undefined symbol: PyExc_TimeoutError
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyTimeoutError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hf64c84a18616a43c) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyTimeoutError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hf64c84a18616a43c) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h82bd90ad606029c6) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h82bd90ad606029c6) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h7ce6f0917406de35) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by exceptions.rs:309 (src/exceptions.rs:309)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h7ce6f0917406de35) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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 "pearson") due to 1 previous error
[INFO] [stdout] error: linking with `cc` failed: exit status: 1
[INFO] [stdout]   |
[INFO] [stdout]   = note:  "cc" "-m64" "/tmp/rustc426Z1e/symbols.o" "<5 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libtest-*,libgetopts-*,librustc_std_workspace_std-*}.rlib" "/opt/rustwide/target/debug/deps/{liblazy_static-3674be3f4245d19b,libggca,libfast_float-615efa375346931c,libenv_logger-6768c135ead1d474,libatty-391c878188a805f6,libtermcolor-cbafc8825e041b3d,libhumantime-9f900d7885b5087e,libregex-b3036468f81da3c3,libregex_automata-105e8535a042310a,libaho_corasick-847080ddcc800a8c,libregex_syntax-b34d0d3f3a197100,libcsv-a4093e49945fb48b,libryu-a980823ac8640001,libitoa-20e94f961f8d160c,libcsv_core-d6ac3c63368d6ac7,libmemchr-08f38e9718637002,libstatrs-7acc1a5f037176e6,libnalgebra-be524c155033124d,librand_distr-2469a3389f497574,libmatrixmultiply-28a888e6c99beb11,librawpointer-10d892ea69c462d6,libnum_rational-8574d91c643bae41,libnum_integer-92829029e93b3980,libtypenum-1862a5dd6fcdc44c,libsimba-0cff735aacb2e553,libwide-a3fb9af7b81a9c93,libsafe_arch-5bf50cf7f85c4749,libbytemuck-78027be639f0e0f7,libnum_complex-48641ed065deb522,librand-99565960cf224d6b,librand_chacha-368639fad3a1c605,libppv_lite86-74d192d5fb0d20a2,librand_core-9c0405eeced83bd6,libgetrandom-8b8aac7d6dc2cc9c,libbincode-20d601ac5080f513,libserde-7e4d81ce70666db4,liblog-368e05ac2c0115e3,libitertools-217b25dfd86c44c6,libpyo3-2045bc840d8b78a7,libmemoffset-797312a586f4d76f,libonce_cell-a1d7742f74efe1da,libpyo3_ffi-65bf35c3ba10ba56,liblibc-81b33709b71653e4,libunindent-ba611b0c58f2b27f,libextsort-2f3433f1f7fd6a22,libtempfile-5eb176ffeba8a342,libfastrand-5e3bec3d1dadb2e4,librustix-83cf1c19c41139d0,libbitflags-c95e5b195a86a9bf,liblinux_raw_sys-07d08e485b51e8af,libcfg_if-3e7fc4e38d4a72b5,librayon-556b83ff68a1cd7e,librayon_core-724bd3cb64d286e7,libcrossbeam_deque-d61e12785107a802,libcrossbeam_epoch-a6cf04f6d42ccc60,libcrossbeam_utils-b6032feb2e6cd592,libeither-b4418dba5a443acb,libapprox-6392729c42cce874,libnum_traits-cae5556ec797c756}.rlib" "<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libstd-*,libpanic_unwind-*,libobject-*,libmemchr-*,libaddr2line-*,libgimli-*,libcfg_if-*,librustc_demangle-*,libstd_detect-*,libhashbrown-*,librustc_std_workspace_alloc-*,libminiz_oxide-*,libadler2-*,libunwind-*,liblibc-*,librustc_std_workspace_core-*,liballoc-*,libcore-*,libcompiler_builtins-*}.rlib" "-Wl,-Bdynamic" "-lgcc_s" "-lutil" "-lrt" "-lpthread" "-lm" "-ldl" "-lc" "-L" "/tmp/rustc426Z1e/raw-dylibs" "-B<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/bin/gcc-ld" "-fuse-ld=lld" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "<sysroot>/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/opt/rustwide/target/debug/deps/kendall-ee91f46c7882aa35" "-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.fa8f62c4babe6a57-cgu.06.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4394d038b1214672) 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.fa8f62c4babe6a57-cgu.06.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4394d038b1214672) in archive /opt/rustwide/target/debug/deps/libggca.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::str::h5a0af419fb3dce12) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::repr::h5d160586697e75e8) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..typeobject..PyType$GT$$u20$as$u20$pyo3..types..typeobject..PyTypeMethods$GT$::name::h8dd2334cc7be7432) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::hb5ee8562845ae686) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::hb5ee8562845ae686) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_string_lossy::h438bc087230b6ba9) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_str::h98a01981de1da149) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.10.rcgu.o:(pyo3::err::panic_after_error::h11fa61957aaba15c) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.10.rcgu.o:(pyo3::err::PyErr::new_type_bound::h875e93204a2e6129) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.10.rcgu.o:(pyo3::err::PyErr::print_panic_and_unwind::h96224d876c13f05e) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.10.rcgu.o:(pyo3::err::PyErr::write_unraisable_bound::h5cd62dcd4a3327a9) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h33179a2a9510c094) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h6bff559bab9aa613) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h82230c5a0e8fa4f0) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced 4 more times
[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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.11.rcgu.o:(pyo3::gil::prepare_freethreaded_python::_$u7b$$u7b$closure$u7d$$u7d$::h6d87348cba17de63) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.rlib
[INFO] [stdout]           >>> referenced by gil.rs:199 (src/gil.rs:199)
[INFO] [stdout]           >>>               pyo3-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.11.rcgu.o:(pyo3::gil::GILGuard::acquire::_$u7b$$u7b$closure$u7d$$u7d$::h7bc404b40c30cf18) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.11.rcgu.o:(pyo3::gil::prepare_freethreaded_python::_$u7b$$u7b$closure$u7d$$u7d$::h6d87348cba17de63) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.11.rcgu.o:(pyo3::gil::prepare_freethreaded_python::_$u7b$$u7b$closure$u7d$$u7d$::h6d87348cba17de63) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.11.rcgu.o:(pyo3::gil::GILGuard::acquire_unchecked::h427772b4a6fb96d2) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.11.rcgu.o:(_$LT$pyo3..gil..GILGuard$u20$as$u20$core..ops..drop..Drop$GT$::drop::hdfc90bc8f81323f1) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::err::err_state::PyErrState::restore::h8ba634a8b933ca78) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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-2045bc840d8b78a7.pyo3.e86a101e26725dc3-cgu.15.rcgu.o:(pyo3::err::err_state::raise_lazy::hd4f5ff9e1410a063) in archive /opt/rustwide/target/debug/deps/libpyo3-2045bc840d8b78a7.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 "kendall") due to 1 previous error
[INFO] running `Command { std: "docker" "inspect" "b6b2fefeb728f762cf621b618a5102b42e96feb90c35e11ee9a6ac860518bc5c", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "b6b2fefeb728f762cf621b618a5102b42e96feb90c35e11ee9a6ac860518bc5c", kill_on_drop: false }`
[INFO] [stdout] b6b2fefeb728f762cf621b618a5102b42e96feb90c35e11ee9a6ac860518bc5c
