[INFO] cloning repository https://github.com/jware-solutions/ggca [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/jware-solutions/ggca" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fjware-solutions%2Fggca", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fjware-solutions%2Fggca'... [INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }` [INFO] [stdout] 69c480abfd4b75c2ce5a56f6c74cab3fca276a05 [INFO] testing jware-solutions/ggca against try#b83b707f97d809763b7861afa7638871f3339a33 for pr-145838-1 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fjware-solutions%2Fggca" "/workspace/builds/worker-4-tc2/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-4-tc2/source'... [INFO] [stderr] done. [INFO] removed /workspace/builds/worker-4-tc2/source/.cargo/config.toml [INFO] started tweaking git repo https://github.com/jware-solutions/ggca [INFO] finished tweaking git repo https://github.com/jware-solutions/ggca [INFO] tweaked toml for git repo https://github.com/jware-solutions/ggca written to /workspace/builds/worker-4-tc2/source/Cargo.toml [INFO] validating manifest of git repo https://github.com/jware-solutions/ggca on toolchain b83b707f97d809763b7861afa7638871f3339a33 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+b83b707f97d809763b7861afa7638871f3339a33" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate git repo https://github.com/jware-solutions/ggca 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" "+b83b707f97d809763b7861afa7638871f3339a33" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-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:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+b83b707f97d809763b7861afa7638871f3339a33" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 2adaac33289030e343b47a9ff4ce7e86da64bb21652a3e7669b4b4cb7e38489f [INFO] running `Command { std: "docker" "start" "-a" "2adaac33289030e343b47a9ff4ce7e86da64bb21652a3e7669b4b4cb7e38489f", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "2adaac33289030e343b47a9ff4ce7e86da64bb21652a3e7669b4b4cb7e38489f", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "2adaac33289030e343b47a9ff4ce7e86da64bb21652a3e7669b4b4cb7e38489f", kill_on_drop: false }` [INFO] [stdout] 2adaac33289030e343b47a9ff4ce7e86da64bb21652a3e7669b4b4cb7e38489f [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+b83b707f97d809763b7861afa7638871f3339a33" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] e1ec3255ac5f39edc36b2d9d6b3b8ffff6b40847492c939802384743ab67027b [INFO] running `Command { std: "docker" "start" "-a" "e1ec3255ac5f39edc36b2d9d6b3b8ffff6b40847492c939802384743ab67027b", kill_on_drop: false }` [INFO] [stderr] Compiling target-lexicon v0.12.15 [INFO] [stderr] Compiling serde v1.0.204 [INFO] [stderr] Compiling libc v0.2.155 [INFO] [stderr] Compiling libm v0.2.8 [INFO] [stderr] Compiling serde_json v1.0.120 [INFO] [stderr] Compiling semver v1.0.23 [INFO] [stderr] Compiling camino v1.1.7 [INFO] [stderr] Compiling num-traits v0.2.19 [INFO] [stderr] Compiling crossbeam-utils v0.8.20 [INFO] [stderr] Compiling error-chain v0.12.4 [INFO] [stderr] Compiling pulldown-cmark v0.9.6 [INFO] [stderr] Compiling syn v2.0.70 [INFO] [stderr] Compiling unicase v2.7.0 [INFO] [stderr] Compiling bytemuck v1.16.1 [INFO] [stderr] Compiling fastrand v2.1.0 [INFO] [stderr] Compiling same-file v1.0.6 [INFO] [stderr] Compiling matrixmultiply v0.3.8 [INFO] [stderr] Compiling walkdir v2.5.0 [INFO] [stderr] Compiling glob v0.3.1 [INFO] [stderr] Compiling bytecount v0.6.8 [INFO] [stderr] Compiling memoffset v0.9.1 [INFO] [stderr] Compiling either v1.13.0 [INFO] [stderr] Compiling rawpointer v0.2.1 [INFO] [stderr] Compiling regex-syntax v0.8.4 [INFO] [stderr] Compiling csv-core v0.1.11 [INFO] [stderr] Compiling itertools v0.9.0 [INFO] [stderr] Compiling fast-float v0.2.0 [INFO] [stderr] Compiling safe_arch v0.7.2 [INFO] [stderr] Compiling tempfile v3.10.1 [INFO] [stderr] Compiling crossbeam-epoch v0.9.18 [INFO] [stderr] Compiling pyo3-build-config v0.22.2 [INFO] [stderr] Compiling wide v0.7.25 [INFO] [stderr] Compiling crossbeam-deque v0.8.5 [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 num-rational v0.4.2 [INFO] [stderr] Compiling regex-automata v0.4.7 [INFO] [stderr] Compiling getrandom v0.2.15 [INFO] [stderr] Compiling atty v0.2.14 [INFO] [stderr] Compiling rand_core v0.6.4 [INFO] [stderr] Compiling rand_chacha v0.3.1 [INFO] [stderr] Compiling pyo3-macros-backend v0.22.2 [INFO] [stderr] Compiling pyo3-ffi v0.22.2 [INFO] [stderr] Compiling pyo3 v0.22.2 [INFO] [stderr] Compiling simba v0.8.1 [INFO] [stderr] Compiling rand v0.8.5 [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 csv v1.3.0 [INFO] [stderr] Compiling bincode v1.3.3 [INFO] [stderr] Compiling cargo_metadata v0.14.2 [INFO] [stderr] Compiling skeptic v0.13.7 [INFO] [stderr] Compiling extsort v0.4.2 [INFO] [stderr] Compiling statrs v0.17.1 [INFO] [stderr] Compiling ggca v1.0.1 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 39.91s [INFO] running `Command { std: "docker" "inspect" "e1ec3255ac5f39edc36b2d9d6b3b8ffff6b40847492c939802384743ab67027b", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "e1ec3255ac5f39edc36b2d9d6b3b8ffff6b40847492c939802384743ab67027b", kill_on_drop: false }` [INFO] [stdout] e1ec3255ac5f39edc36b2d9d6b3b8ffff6b40847492c939802384743ab67027b [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+b83b707f97d809763b7861afa7638871f3339a33" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 594e8d85040eb161cc74cedb6b96a7243d0b9d88bff7ea47bb0e70161669a148 [INFO] running `Command { std: "docker" "start" "-a" "594e8d85040eb161cc74cedb6b96a7243d0b9d88bff7ea47bb0e70161669a148", 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_builder v4.5.9 [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 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 clap v4.5.9 [INFO] [stderr] Compiling criterion v0.5.1 [INFO] [stderr] Compiling skeptic v0.13.7 [INFO] [stderr] Compiling extsort v0.4.2 [INFO] [stderr] Compiling ggca v1.0.1 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | / create_exception!( [INFO] [stdout] 125 | | ggca, [INFO] [stdout] 126 | | InvalidCorrelationMethod, [INFO] [stdout] 127 | | pyo3::exceptions::PyException [INFO] [stdout] 128 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/lib.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | create_exception!(ggca, InvalidAdjustmentMethod, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | create_exception!(ggca, GGCADiffSamplesLength, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/analysis.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | create_exception!(ggca, GGCADiffSamples, pyo3::exceptions::PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> src/dataset.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(ggca, GGCAError, PyException); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `extension-module` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: linking with `cc` failed: exit status: 1 [INFO] [stdout] | [INFO] [stdout] = note: "cc" "-m64" "/tmp/rustcjBTkOq/symbols.o" "<2 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "/opt/rustwide/target/debug/deps/{libggca,libfast_float-a001eccc39083970,libenv_logger-76fcdf77ea9f7fc1,libatty-446cf219abaafef1,libtermcolor-96a9ed65821a6544,libhumantime-271ba35809dd8c72,libregex-3a86ec74e2934591,libregex_automata-f88760a5be8fa511,libaho_corasick-5318fee7af990b33,libregex_syntax-c7888ad363b60cdf,libcsv-a93bbec86841011e,libryu-f8ba606093049f91,libitoa-4c6598116a867907,libcsv_core-fd1e44616b471c08,libmemchr-3ffe5f7a52883367,libstatrs-1c139a6ad8d13ebe,libnalgebra-f6b78f08f4d7e7af,librand_distr-1867bfaa9a800d1d,libmatrixmultiply-34c291336c5e5078,librawpointer-a726d041f28ef5ec,libnum_rational-e08db830b321ca16,libnum_integer-66fa67c4a502ae8f,libtypenum-66c155be53855aa0,libsimba-36107f7479bda9aa,libwide-4266911880668b24,libsafe_arch-257465445e9c44ab,libbytemuck-5dc727f1fbeada00,libnum_complex-6353647e9164a061,librand-d95a8b9a6596c1c9,librand_chacha-eae2157c7b3ff45b,libppv_lite86-4250c766b4729968,librand_core-e1a3406510404d96,libgetrandom-3c8cbe44d6a2de0f,libapprox-1db83cb060b5d953,libnum_traits-0fc677e4164f53eb,libbincode-af56573e0b0292dc,libserde-4330823f1076d928,liblog-669e9396cafcbb01,libitertools-54701bdaf7439916,libpyo3-b6285408a3ede724,libmemoffset-eff8dc08e7f61fc4,libonce_cell-24c5d665b6879050,libpyo3_ffi-e1301dbc9bf3455b,liblibc-04709b2177888c94,libunindent-df02e22db51b2e3a,libextsort-6e3c0ffa899e5cff,libtempfile-4c3b086491d53c1e,libfastrand-9c5266858c813c39,librustix-d5336887fb8496af,libbitflags-eb92e23a18d5cc91,liblinux_raw_sys-dd10f1d1b50fcb6c,libcfg_if-33ef6c02a07f9fec,librayon-d7f70122059d9405,librayon_core-936d6cd684097949,libcrossbeam_deque-1677f27c8a0deac5,libcrossbeam_epoch-3554ccb4a3bc7b51,libcrossbeam_utils-eb4587c77878a9d5,libeither-38d43fea6173fdf6}.rlib" "/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/rustcjBTkOq/raw-dylibs" "-B/lib/rustlib/x86_64-unknown-linux-gnu/bin/gcc-ld" "-fuse-ld=lld" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/opt/rustwide/target/debug/examples/basic-d5b5aed37cd87172" "-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.dea1c3f029bd61af-cgu.03.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h529af643688a14a2) 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.dea1c3f029bd61af-cgu.03.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h529af643688a14a2) in archive /opt/rustwide/target/debug/deps/libggca.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.10.rcgu.o:(pyo3::err::panic_after_error::hf7e3b216a274e63c) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.10.rcgu.o:(pyo3::err::PyErr::new_type_bound::h02a2b61304d945f4) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.10.rcgu.o:(pyo3::err::PyErr::print_panic_and_unwind::h7723ce9dbb73746f) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.10.rcgu.o:(pyo3::err::PyErr::write_unraisable_bound::h348dfc5405cafe47) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.08.rcgu.o:(pyo3::gil::ReferencePool::update_counts::hb0225e68a5a5e75c) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.08.rcgu.o:(pyo3::gil::register_decref::hc4623c961948fa4c) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h6b8a62a7363d740c) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.08.rcgu.o:(pyo3::gil::prepare_freethreaded_python::_$u7b$$u7b$closure$u7d$$u7d$::he36b859aa9b850e2) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by gil.rs:199 (src/gil.rs:199) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.08.rcgu.o:(pyo3::gil::GILGuard::acquire::_$u7b$$u7b$closure$u7d$$u7d$::hcda36ec4013efc16) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.08.rcgu.o:(pyo3::gil::prepare_freethreaded_python::_$u7b$$u7b$closure$u7d$$u7d$::he36b859aa9b850e2) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.08.rcgu.o:(pyo3::gil::prepare_freethreaded_python::_$u7b$$u7b$closure$u7d$$u7d$::he36b859aa9b850e2) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.08.rcgu.o:(pyo3::gil::GILGuard::acquire_unchecked::he09daf3a0be7f432) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.08.rcgu.o:(_$LT$pyo3..gil..GILGuard$u20$as$u20$core..ops..drop..Drop$GT$::drop::he643ff0f8cff7ee0) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::PyErrState::restore::h796ec4199d7f3a6d) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::raise_lazy::he3a6c64f2f2e3603) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::raise_lazy::he3a6c64f2f2e3603) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::ptraceback::hcb2e15f882610ba8) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::take::h52e199607d533b73) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::types::string::PyString::new_bound::habd8ce808f89a2df) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hd54d50ae5c828cbf) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hd54d50ae5c828cbf) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h12ec5b38b0ce7543) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h12ec5b38b0ce7543) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyTimeoutError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::haa642168132fa38f) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyTimeoutError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::haa642168132fa38f) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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/rustc67Euo9/symbols.o" "<2 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libtest-*,libgetopts-*,libunicode_width-*,librustc_std_workspace_std-*}.rlib" "/opt/rustwide/target/debug/deps/{liblazy_static-b3603208c0de2608,libggca,libfast_float-a001eccc39083970,libenv_logger-76fcdf77ea9f7fc1,libatty-446cf219abaafef1,libtermcolor-96a9ed65821a6544,libhumantime-271ba35809dd8c72,libregex-3a86ec74e2934591,libregex_automata-f88760a5be8fa511,libaho_corasick-5318fee7af990b33,libregex_syntax-c7888ad363b60cdf,libcsv-a93bbec86841011e,libryu-f8ba606093049f91,libitoa-4c6598116a867907,libcsv_core-fd1e44616b471c08,libmemchr-3ffe5f7a52883367,libstatrs-1c139a6ad8d13ebe,libnalgebra-f6b78f08f4d7e7af,librand_distr-1867bfaa9a800d1d,libmatrixmultiply-34c291336c5e5078,librawpointer-a726d041f28ef5ec,libnum_rational-e08db830b321ca16,libnum_integer-66fa67c4a502ae8f,libtypenum-66c155be53855aa0,libsimba-36107f7479bda9aa,libwide-4266911880668b24,libsafe_arch-257465445e9c44ab,libbytemuck-5dc727f1fbeada00,libnum_complex-6353647e9164a061,librand-d95a8b9a6596c1c9,librand_chacha-eae2157c7b3ff45b,libppv_lite86-4250c766b4729968,librand_core-e1a3406510404d96,libgetrandom-3c8cbe44d6a2de0f,libbincode-af56573e0b0292dc,libserde-4330823f1076d928,liblog-669e9396cafcbb01,libitertools-54701bdaf7439916,libpyo3-b6285408a3ede724,libmemoffset-eff8dc08e7f61fc4,libonce_cell-24c5d665b6879050,libpyo3_ffi-e1301dbc9bf3455b,liblibc-04709b2177888c94,libunindent-df02e22db51b2e3a,libextsort-6e3c0ffa899e5cff,libtempfile-4c3b086491d53c1e,libfastrand-9c5266858c813c39,librustix-d5336887fb8496af,libbitflags-eb92e23a18d5cc91,liblinux_raw_sys-dd10f1d1b50fcb6c,libcfg_if-33ef6c02a07f9fec,librayon-d7f70122059d9405,librayon_core-936d6cd684097949,libcrossbeam_deque-1677f27c8a0deac5,libcrossbeam_epoch-3554ccb4a3bc7b51,libcrossbeam_utils-eb4587c77878a9d5,libeither-38d43fea6173fdf6,libapprox-1db83cb060b5d953,libnum_traits-0fc677e4164f53eb}.rlib" "/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/rustc67Euo9/raw-dylibs" "-B/lib/rustlib/x86_64-unknown-linux-gnu/bin/gcc-ld" "-fuse-ld=lld" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/opt/rustwide/target/debug/deps/cpg_site_ids-a1a898464339ed30" "-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.dea1c3f029bd61af-cgu.03.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h529af643688a14a2) 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.dea1c3f029bd61af-cgu.03.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h529af643688a14a2) 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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::str::h442586f5934ad695) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::repr::h68b192838bd437ac) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..typeobject..PyType$GT$$u20$as$u20$pyo3..types..typeobject..PyTypeMethods$GT$::name::hf7f2d829054057bb) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::h7b205f6216f21001) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::h7b205f6216f21001) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_string_lossy::hcc904a35f6f4f7e4) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_str::hd7920f37baaf1b47) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h6b8a62a7363d740c) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h9128d76d71bc61d6) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::hc6b10bcbb1014d9f) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::PyErrState::restore::h796ec4199d7f3a6d) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::raise_lazy::he3a6c64f2f2e3603) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::raise_lazy::he3a6c64f2f2e3603) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::ptraceback::hcb2e15f882610ba8) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::take::h52e199607d533b73) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::types::string::PyString::new_bound::habd8ce808f89a2df) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hd54d50ae5c828cbf) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hd54d50ae5c828cbf) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h12ec5b38b0ce7543) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h12ec5b38b0ce7543) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyTimeoutError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::haa642168132fa38f) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyTimeoutError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::haa642168132fa38f) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4150d35ed44ef287) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4150d35ed44ef287) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h8dde6cd45eed586b) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h8dde6cd45eed586b) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: too many errors emitted, stopping now (use --error-limit=0 to see all errors) [INFO] [stdout] collect2: error: ld returned 1 exit status [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `ggca` (example "basic") due to 1 previous error [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] [stdout] error: linking with `cc` failed: exit status: 1 [INFO] [stdout] | [INFO] [stdout] = note: "cc" "-m64" "/tmp/rustcFHXFrI/symbols.o" "<2 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "/opt/rustwide/target/debug/deps/{libggca,libfast_float-a001eccc39083970,libenv_logger-76fcdf77ea9f7fc1,libatty-446cf219abaafef1,libtermcolor-96a9ed65821a6544,libhumantime-271ba35809dd8c72,libregex-3a86ec74e2934591,libregex_automata-f88760a5be8fa511,libaho_corasick-5318fee7af990b33,libregex_syntax-c7888ad363b60cdf,libcsv-a93bbec86841011e,libryu-f8ba606093049f91,libitoa-4c6598116a867907,libcsv_core-fd1e44616b471c08,libmemchr-3ffe5f7a52883367,libstatrs-1c139a6ad8d13ebe,libnalgebra-f6b78f08f4d7e7af,librand_distr-1867bfaa9a800d1d,libmatrixmultiply-34c291336c5e5078,librawpointer-a726d041f28ef5ec,libnum_rational-e08db830b321ca16,libnum_integer-66fa67c4a502ae8f,libtypenum-66c155be53855aa0,libsimba-36107f7479bda9aa,libwide-4266911880668b24,libsafe_arch-257465445e9c44ab,libbytemuck-5dc727f1fbeada00,libnum_complex-6353647e9164a061,librand-d95a8b9a6596c1c9,librand_chacha-eae2157c7b3ff45b,libppv_lite86-4250c766b4729968,librand_core-e1a3406510404d96,libgetrandom-3c8cbe44d6a2de0f,libapprox-1db83cb060b5d953,libnum_traits-0fc677e4164f53eb,libbincode-af56573e0b0292dc,libserde-4330823f1076d928,liblog-669e9396cafcbb01,libitertools-54701bdaf7439916,libpyo3-b6285408a3ede724,libmemoffset-eff8dc08e7f61fc4,libonce_cell-24c5d665b6879050,libpyo3_ffi-e1301dbc9bf3455b,liblibc-04709b2177888c94,libunindent-df02e22db51b2e3a,libextsort-6e3c0ffa899e5cff,libtempfile-4c3b086491d53c1e,libfastrand-9c5266858c813c39,librustix-d5336887fb8496af,libbitflags-eb92e23a18d5cc91,liblinux_raw_sys-dd10f1d1b50fcb6c,libcfg_if-33ef6c02a07f9fec,librayon-d7f70122059d9405,librayon_core-936d6cd684097949,libcrossbeam_deque-1677f27c8a0deac5,libcrossbeam_epoch-3554ccb4a3bc7b51,libcrossbeam_utils-eb4587c77878a9d5,libeither-38d43fea6173fdf6}.rlib" "/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/rustcFHXFrI/raw-dylibs" "-B/lib/rustlib/x86_64-unknown-linux-gnu/bin/gcc-ld" "-fuse-ld=lld" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/opt/rustwide/target/debug/examples/cpg_site_ids-b5cfcccb68189a1b" "-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.dea1c3f029bd61af-cgu.03.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h529af643688a14a2) 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.dea1c3f029bd61af-cgu.03.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h529af643688a14a2) 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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::str::h442586f5934ad695) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::repr::h68b192838bd437ac) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..typeobject..PyType$GT$$u20$as$u20$pyo3..types..typeobject..PyTypeMethods$GT$::name::hf7f2d829054057bb) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::h7b205f6216f21001) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::h7b205f6216f21001) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_string_lossy::hcc904a35f6f4f7e4) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_str::hd7920f37baaf1b47) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h6b8a62a7363d740c) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h9128d76d71bc61d6) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::hc6b10bcbb1014d9f) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::PyErrState::restore::h796ec4199d7f3a6d) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::raise_lazy::he3a6c64f2f2e3603) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::raise_lazy::he3a6c64f2f2e3603) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::ptraceback::hcb2e15f882610ba8) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::take::h52e199607d533b73) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::types::string::PyString::new_bound::habd8ce808f89a2df) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hd54d50ae5c828cbf) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hd54d50ae5c828cbf) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h12ec5b38b0ce7543) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h12ec5b38b0ce7543) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyTimeoutError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::haa642168132fa38f) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyTimeoutError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::haa642168132fa38f) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4150d35ed44ef287) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4150d35ed44ef287) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h8dde6cd45eed586b) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h8dde6cd45eed586b) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: too many errors emitted, stopping now (use --error-limit=0 to see all errors) [INFO] [stdout] collect2: error: ld returned 1 exit status [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `ggca` (test "cpg_site_ids") due to 1 previous error [INFO] [stderr] error: could not compile `ggca` (example "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/rustcnfJcd8/symbols.o" "<5 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libtest-*,libgetopts-*,libunicode_width-*,librustc_std_workspace_std-*}.rlib" "/opt/rustwide/target/debug/deps/{liblazy_static-b3603208c0de2608,libggca,libfast_float-a001eccc39083970,libenv_logger-76fcdf77ea9f7fc1,libatty-446cf219abaafef1,libtermcolor-96a9ed65821a6544,libhumantime-271ba35809dd8c72,libregex-3a86ec74e2934591,libregex_automata-f88760a5be8fa511,libaho_corasick-5318fee7af990b33,libregex_syntax-c7888ad363b60cdf,libcsv-a93bbec86841011e,libryu-f8ba606093049f91,libitoa-4c6598116a867907,libcsv_core-fd1e44616b471c08,libmemchr-3ffe5f7a52883367,libstatrs-1c139a6ad8d13ebe,libnalgebra-f6b78f08f4d7e7af,librand_distr-1867bfaa9a800d1d,libmatrixmultiply-34c291336c5e5078,librawpointer-a726d041f28ef5ec,libnum_rational-e08db830b321ca16,libnum_integer-66fa67c4a502ae8f,libtypenum-66c155be53855aa0,libsimba-36107f7479bda9aa,libwide-4266911880668b24,libsafe_arch-257465445e9c44ab,libbytemuck-5dc727f1fbeada00,libnum_complex-6353647e9164a061,librand-d95a8b9a6596c1c9,librand_chacha-eae2157c7b3ff45b,libppv_lite86-4250c766b4729968,librand_core-e1a3406510404d96,libgetrandom-3c8cbe44d6a2de0f,libbincode-af56573e0b0292dc,libserde-4330823f1076d928,liblog-669e9396cafcbb01,libitertools-54701bdaf7439916,libpyo3-b6285408a3ede724,libmemoffset-eff8dc08e7f61fc4,libonce_cell-24c5d665b6879050,libpyo3_ffi-e1301dbc9bf3455b,liblibc-04709b2177888c94,libunindent-df02e22db51b2e3a,libextsort-6e3c0ffa899e5cff,libtempfile-4c3b086491d53c1e,libfastrand-9c5266858c813c39,librustix-d5336887fb8496af,libbitflags-eb92e23a18d5cc91,liblinux_raw_sys-dd10f1d1b50fcb6c,libcfg_if-33ef6c02a07f9fec,librayon-d7f70122059d9405,librayon_core-936d6cd684097949,libcrossbeam_deque-1677f27c8a0deac5,libcrossbeam_epoch-3554ccb4a3bc7b51,libcrossbeam_utils-eb4587c77878a9d5,libeither-38d43fea6173fdf6,libapprox-1db83cb060b5d953,libnum_traits-0fc677e4164f53eb}.rlib" "/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/rustcnfJcd8/raw-dylibs" "-B/lib/rustlib/x86_64-unknown-linux-gnu/bin/gcc-ld" "-fuse-ld=lld" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/opt/rustwide/target/debug/deps/spearman-5b037f41775fbe1a" "-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.dea1c3f029bd61af-cgu.03.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h529af643688a14a2) 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.dea1c3f029bd61af-cgu.03.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h529af643688a14a2) 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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::str::h442586f5934ad695) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::repr::h68b192838bd437ac) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..typeobject..PyType$GT$$u20$as$u20$pyo3..types..typeobject..PyTypeMethods$GT$::name::hf7f2d829054057bb) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::PyErrState::restore::h796ec4199d7f3a6d) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::raise_lazy::he3a6c64f2f2e3603) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::raise_lazy::he3a6c64f2f2e3603) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::ptraceback::hcb2e15f882610ba8) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::h7b205f6216f21001) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::take::h52e199607d533b73) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::h7b205f6216f21001) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_string_lossy::hcc904a35f6f4f7e4) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::types::string::PyString::new_bound::habd8ce808f89a2df) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_str::hd7920f37baaf1b47) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hd54d50ae5c828cbf) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hd54d50ae5c828cbf) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h12ec5b38b0ce7543) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h12ec5b38b0ce7543) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyTimeoutError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::haa642168132fa38f) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyTimeoutError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::haa642168132fa38f) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4150d35ed44ef287) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4150d35ed44ef287) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h8dde6cd45eed586b) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h8dde6cd45eed586b) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyBrokenPipeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h9bab263607adb47e) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyBrokenPipeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h9bab263607adb47e) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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/rustc97UZcS/symbols.o" "<2 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libtest-*,libgetopts-*,libunicode_width-*,librustc_std_workspace_std-*}.rlib" "/opt/rustwide/target/debug/deps/{libggca,libfast_float-a001eccc39083970,libenv_logger-76fcdf77ea9f7fc1,libatty-446cf219abaafef1,libtermcolor-96a9ed65821a6544,libhumantime-271ba35809dd8c72,libregex-3a86ec74e2934591,libregex_automata-f88760a5be8fa511,libaho_corasick-5318fee7af990b33,libregex_syntax-c7888ad363b60cdf,libcsv-a93bbec86841011e,libryu-f8ba606093049f91,libitoa-4c6598116a867907,libcsv_core-fd1e44616b471c08,libmemchr-3ffe5f7a52883367,libstatrs-1c139a6ad8d13ebe,libnalgebra-f6b78f08f4d7e7af,librand_distr-1867bfaa9a800d1d,libmatrixmultiply-34c291336c5e5078,librawpointer-a726d041f28ef5ec,libnum_rational-e08db830b321ca16,libnum_integer-66fa67c4a502ae8f,libtypenum-66c155be53855aa0,libsimba-36107f7479bda9aa,libwide-4266911880668b24,libsafe_arch-257465445e9c44ab,libbytemuck-5dc727f1fbeada00,libnum_complex-6353647e9164a061,librand-d95a8b9a6596c1c9,librand_chacha-eae2157c7b3ff45b,libppv_lite86-4250c766b4729968,librand_core-e1a3406510404d96,libgetrandom-3c8cbe44d6a2de0f,libbincode-af56573e0b0292dc,libserde-4330823f1076d928,liblog-669e9396cafcbb01,libitertools-54701bdaf7439916,libpyo3-b6285408a3ede724,libmemoffset-eff8dc08e7f61fc4,libonce_cell-24c5d665b6879050,libpyo3_ffi-e1301dbc9bf3455b,liblibc-04709b2177888c94,libunindent-df02e22db51b2e3a,libextsort-6e3c0ffa899e5cff,libtempfile-4c3b086491d53c1e,libfastrand-9c5266858c813c39,librustix-d5336887fb8496af,libbitflags-eb92e23a18d5cc91,liblinux_raw_sys-dd10f1d1b50fcb6c,libcfg_if-33ef6c02a07f9fec,librayon-d7f70122059d9405,librayon_core-936d6cd684097949,libcrossbeam_deque-1677f27c8a0deac5,libcrossbeam_epoch-3554ccb4a3bc7b51,libcrossbeam_utils-eb4587c77878a9d5,libeither-38d43fea6173fdf6,libapprox-1db83cb060b5d953,libnum_traits-0fc677e4164f53eb}.rlib" "/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/rustc97UZcS/raw-dylibs" "-B/lib/rustlib/x86_64-unknown-linux-gnu/bin/gcc-ld" "-fuse-ld=lld" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/opt/rustwide/target/debug/deps/nan_filtering-010bcdba3538ee32" "-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.dea1c3f029bd61af-cgu.03.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h529af643688a14a2) 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.dea1c3f029bd61af-cgu.03.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h529af643688a14a2) 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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::str::h442586f5934ad695) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::repr::h68b192838bd437ac) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..typeobject..PyType$GT$$u20$as$u20$pyo3..types..typeobject..PyTypeMethods$GT$::name::hf7f2d829054057bb) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::h7b205f6216f21001) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::h7b205f6216f21001) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_string_lossy::hcc904a35f6f4f7e4) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_str::hd7920f37baaf1b47) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h6b8a62a7363d740c) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h9128d76d71bc61d6) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::hc6b10bcbb1014d9f) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::PyErrState::restore::h796ec4199d7f3a6d) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::raise_lazy::he3a6c64f2f2e3603) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::raise_lazy::he3a6c64f2f2e3603) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::ptraceback::hcb2e15f882610ba8) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::take::h52e199607d533b73) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::types::string::PyString::new_bound::habd8ce808f89a2df) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hd54d50ae5c828cbf) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hd54d50ae5c828cbf) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h12ec5b38b0ce7543) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h12ec5b38b0ce7543) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyTimeoutError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::haa642168132fa38f) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyTimeoutError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::haa642168132fa38f) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4150d35ed44ef287) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4150d35ed44ef287) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h8dde6cd45eed586b) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h8dde6cd45eed586b) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] [INFO] [stdout] rust-lld: error: too many errors emitted, stopping now (use --error-limit=0 to see all errors) [INFO] [stdout] collect2: error: ld returned 1 exit status [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `ggca` (test "nan_filtering") due to 1 previous error [INFO] [stdout] error: linking with `cc` failed: exit status: 1 [INFO] [stdout] | [INFO] [stdout] = note: "cc" "-m64" "/tmp/rustcp3TgCt/symbols.o" "<4 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libtest-*,libgetopts-*,libunicode_width-*,librustc_std_workspace_std-*}.rlib" "/opt/rustwide/target/debug/deps/{liblazy_static-b3603208c0de2608,libggca,libfast_float-a001eccc39083970,libenv_logger-76fcdf77ea9f7fc1,libatty-446cf219abaafef1,libtermcolor-96a9ed65821a6544,libhumantime-271ba35809dd8c72,libregex-3a86ec74e2934591,libregex_automata-f88760a5be8fa511,libaho_corasick-5318fee7af990b33,libregex_syntax-c7888ad363b60cdf,libcsv-a93bbec86841011e,libryu-f8ba606093049f91,libitoa-4c6598116a867907,libcsv_core-fd1e44616b471c08,libmemchr-3ffe5f7a52883367,libstatrs-1c139a6ad8d13ebe,libnalgebra-f6b78f08f4d7e7af,librand_distr-1867bfaa9a800d1d,libmatrixmultiply-34c291336c5e5078,librawpointer-a726d041f28ef5ec,libnum_rational-e08db830b321ca16,libnum_integer-66fa67c4a502ae8f,libtypenum-66c155be53855aa0,libsimba-36107f7479bda9aa,libwide-4266911880668b24,libsafe_arch-257465445e9c44ab,libbytemuck-5dc727f1fbeada00,libnum_complex-6353647e9164a061,librand-d95a8b9a6596c1c9,librand_chacha-eae2157c7b3ff45b,libppv_lite86-4250c766b4729968,librand_core-e1a3406510404d96,libgetrandom-3c8cbe44d6a2de0f,libbincode-af56573e0b0292dc,libserde-4330823f1076d928,liblog-669e9396cafcbb01,libitertools-54701bdaf7439916,libpyo3-b6285408a3ede724,libmemoffset-eff8dc08e7f61fc4,libonce_cell-24c5d665b6879050,libpyo3_ffi-e1301dbc9bf3455b,liblibc-04709b2177888c94,libunindent-df02e22db51b2e3a,libextsort-6e3c0ffa899e5cff,libtempfile-4c3b086491d53c1e,libfastrand-9c5266858c813c39,librustix-d5336887fb8496af,libbitflags-eb92e23a18d5cc91,liblinux_raw_sys-dd10f1d1b50fcb6c,libcfg_if-33ef6c02a07f9fec,librayon-d7f70122059d9405,librayon_core-936d6cd684097949,libcrossbeam_deque-1677f27c8a0deac5,libcrossbeam_epoch-3554ccb4a3bc7b51,libcrossbeam_utils-eb4587c77878a9d5,libeither-38d43fea6173fdf6,libapprox-1db83cb060b5d953,libnum_traits-0fc677e4164f53eb}.rlib" "/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/rustcp3TgCt/raw-dylibs" "-B/lib/rustlib/x86_64-unknown-linux-gnu/bin/gcc-ld" "-fuse-ld=lld" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/opt/rustwide/target/debug/deps/pearson-9eb28e28a2c8329d" "-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.dea1c3f029bd61af-cgu.03.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h529af643688a14a2) 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.dea1c3f029bd61af-cgu.03.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h529af643688a14a2) 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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::str::h442586f5934ad695) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::repr::h68b192838bd437ac) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..typeobject..PyType$GT$$u20$as$u20$pyo3..types..typeobject..PyTypeMethods$GT$::name::hf7f2d829054057bb) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::h7b205f6216f21001) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::h7b205f6216f21001) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_string_lossy::hcc904a35f6f4f7e4) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_str::hd7920f37baaf1b47) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h6b8a62a7363d740c) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h9128d76d71bc61d6) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::hc6b10bcbb1014d9f) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::PyErrState::restore::h796ec4199d7f3a6d) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::raise_lazy::he3a6c64f2f2e3603) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::raise_lazy::he3a6c64f2f2e3603) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::ptraceback::hcb2e15f882610ba8) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::take::h52e199607d533b73) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::types::string::PyString::new_bound::habd8ce808f89a2df) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.10.rcgu.o:(pyo3::err::panic_after_error::hf7e3b216a274e63c) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.10.rcgu.o:(pyo3::err::PyErr::new_type_bound::h02a2b61304d945f4) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.10.rcgu.o:(pyo3::err::PyErr::print_panic_and_unwind::h7723ce9dbb73746f) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.10.rcgu.o:(pyo3::err::PyErr::write_unraisable_bound::h348dfc5405cafe47) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.08.rcgu.o:(pyo3::gil::prepare_freethreaded_python::_$u7b$$u7b$closure$u7d$$u7d$::he36b859aa9b850e2) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by gil.rs:199 (src/gil.rs:199) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.08.rcgu.o:(pyo3::gil::GILGuard::acquire::_$u7b$$u7b$closure$u7d$$u7d$::hcda36ec4013efc16) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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/rustcm2EPWp/symbols.o" "<5 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "/lib/rustlib/x86_64-unknown-linux-gnu/lib/{libtest-*,libgetopts-*,libunicode_width-*,librustc_std_workspace_std-*}.rlib" "/opt/rustwide/target/debug/deps/{liblazy_static-b3603208c0de2608,libggca,libfast_float-a001eccc39083970,libenv_logger-76fcdf77ea9f7fc1,libatty-446cf219abaafef1,libtermcolor-96a9ed65821a6544,libhumantime-271ba35809dd8c72,libregex-3a86ec74e2934591,libregex_automata-f88760a5be8fa511,libaho_corasick-5318fee7af990b33,libregex_syntax-c7888ad363b60cdf,libcsv-a93bbec86841011e,libryu-f8ba606093049f91,libitoa-4c6598116a867907,libcsv_core-fd1e44616b471c08,libmemchr-3ffe5f7a52883367,libstatrs-1c139a6ad8d13ebe,libnalgebra-f6b78f08f4d7e7af,librand_distr-1867bfaa9a800d1d,libmatrixmultiply-34c291336c5e5078,librawpointer-a726d041f28ef5ec,libnum_rational-e08db830b321ca16,libnum_integer-66fa67c4a502ae8f,libtypenum-66c155be53855aa0,libsimba-36107f7479bda9aa,libwide-4266911880668b24,libsafe_arch-257465445e9c44ab,libbytemuck-5dc727f1fbeada00,libnum_complex-6353647e9164a061,librand-d95a8b9a6596c1c9,librand_chacha-eae2157c7b3ff45b,libppv_lite86-4250c766b4729968,librand_core-e1a3406510404d96,libgetrandom-3c8cbe44d6a2de0f,libbincode-af56573e0b0292dc,libserde-4330823f1076d928,liblog-669e9396cafcbb01,libitertools-54701bdaf7439916,libpyo3-b6285408a3ede724,libmemoffset-eff8dc08e7f61fc4,libonce_cell-24c5d665b6879050,libpyo3_ffi-e1301dbc9bf3455b,liblibc-04709b2177888c94,libunindent-df02e22db51b2e3a,libextsort-6e3c0ffa899e5cff,libtempfile-4c3b086491d53c1e,libfastrand-9c5266858c813c39,librustix-d5336887fb8496af,libbitflags-eb92e23a18d5cc91,liblinux_raw_sys-dd10f1d1b50fcb6c,libcfg_if-33ef6c02a07f9fec,librayon-d7f70122059d9405,librayon_core-936d6cd684097949,libcrossbeam_deque-1677f27c8a0deac5,libcrossbeam_epoch-3554ccb4a3bc7b51,libcrossbeam_utils-eb4587c77878a9d5,libeither-38d43fea6173fdf6,libapprox-1db83cb060b5d953,libnum_traits-0fc677e4164f53eb}.rlib" "/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/rustcm2EPWp/raw-dylibs" "-B/lib/rustlib/x86_64-unknown-linux-gnu/bin/gcc-ld" "-fuse-ld=lld" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/opt/rustwide/target/debug/deps/kendall-a303546981b092e2" "-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.dea1c3f029bd61af-cgu.03.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h529af643688a14a2) 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.dea1c3f029bd61af-cgu.03.rcgu.o:(_$LT$pyo3..exceptions..PyException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h529af643688a14a2) 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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::str::h442586f5934ad695) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..any..PyAny$GT$$u20$as$u20$pyo3..types..any..PyAnyMethods$GT$::repr::h68b192838bd437ac) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$pyo3..types..typeobject..PyType$GT$$u20$as$u20$pyo3..types..typeobject..PyTypeMethods$GT$::name::hf7f2d829054057bb) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::h7b205f6216f21001) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(pyo3::types::bytes::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..bytes..PyBytes$GT$$GT$::as_bytes::h7b205f6216f21001) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_string_lossy::hcc904a35f6f4f7e4) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(pyo3::types::string::_$LT$impl$u20$pyo3..instance..Borrowed$LT$pyo3..types..string..PyString$GT$$GT$::to_str::hd7920f37baaf1b47) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h6b8a62a7363d740c) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h9128d76d71bc61d6) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.00.rcgu.o:(_$LT$pyo3..instance..Bound$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::hc6b10bcbb1014d9f) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::PyErrState::restore::h796ec4199d7f3a6d) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::raise_lazy::he3a6c64f2f2e3603) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::raise_lazy::he3a6c64f2f2e3603) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::ptraceback::hcb2e15f882610ba8) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::err::err_state::PyErrStateNormalized::take::h52e199607d533b73) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(pyo3::types::string::PyString::new_bound::habd8ce808f89a2df) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hd54d50ae5c828cbf) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyOSError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::hd54d50ae5c828cbf) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h12ec5b38b0ce7543) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyTypeError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h12ec5b38b0ce7543) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyTimeoutError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::haa642168132fa38f) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyTimeoutError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::haa642168132fa38f) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4150d35ed44ef287) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyBaseException$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h4150d35ed44ef287) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h8dde6cd45eed586b) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.rlib [INFO] [stdout] >>> referenced by exceptions.rs:309 (src/exceptions.rs:309) [INFO] [stdout] >>> pyo3-b6285408a3ede724.pyo3.635211f1fe37f993-cgu.04.rcgu.o:(_$LT$pyo3..exceptions..PyBlockingIOError$u20$as$u20$pyo3..type_object..PyTypeInfo$GT$::type_object_raw::_$u7b$$u7b$closure$u7d$$u7d$::h8dde6cd45eed586b) in archive /opt/rustwide/target/debug/deps/libpyo3-b6285408a3ede724.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" "594e8d85040eb161cc74cedb6b96a7243d0b9d88bff7ea47bb0e70161669a148", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "594e8d85040eb161cc74cedb6b96a7243d0b9d88bff7ea47bb0e70161669a148", kill_on_drop: false }` [INFO] [stdout] 594e8d85040eb161cc74cedb6b96a7243d0b9d88bff7ea47bb0e70161669a148