[INFO] cloning repository https://github.com/SWE-Gym-Raw/qiskit__qiskit [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/SWE-Gym-Raw/qiskit__qiskit" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FSWE-Gym-Raw%2Fqiskit__qiskit", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FSWE-Gym-Raw%2Fqiskit__qiskit'... [INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }` [INFO] [stdout] 9fc58916d132777fb505dc718c3ca403ee72f316 [INFO] checking SWE-Gym-Raw/qiskit__qiskit against try#4797991aa2efb6d658150f10425b3f3b5d10eceb for pr-143193 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FSWE-Gym-Raw%2Fqiskit__qiskit" "/workspace/builds/worker-7-tc2/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-7-tc2/source'... [INFO] [stderr] done. [INFO] removed /workspace/builds/worker-7-tc2/source/.cargo/config.toml [INFO] removed /workspace/builds/worker-7-tc2/source/rust-toolchain.toml [INFO] started tweaking git repo https://github.com/SWE-Gym-Raw/qiskit__qiskit [INFO] finished tweaking git repo https://github.com/SWE-Gym-Raw/qiskit__qiskit [INFO] tweaked toml for git repo https://github.com/SWE-Gym-Raw/qiskit__qiskit written to /workspace/builds/worker-7-tc2/source/Cargo.toml [INFO] validating manifest of git repo https://github.com/SWE-Gym-Raw/qiskit__qiskit on toolchain 4797991aa2efb6d658150f10425b3f3b5d10eceb [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+4797991aa2efb6d658150f10425b3f3b5d10eceb" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate git repo https://github.com/SWE-Gym-Raw/qiskit__qiskit 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" "+4797991aa2efb6d658150f10425b3f3b5d10eceb" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-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:cf8efcab8866f2cf4285301c7418e2f4f2a9b088c91ba69c40d5b659f81557f7" "/opt/rustwide/cargo-home/bin/cargo" "+4797991aa2efb6d658150f10425b3f3b5d10eceb" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 0dc332165fa80b5b865eaa36d14550057eda30492738cedca13b13bf3a9889eb [INFO] running `Command { std: "docker" "start" "-a" "0dc332165fa80b5b865eaa36d14550057eda30492738cedca13b13bf3a9889eb", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "0dc332165fa80b5b865eaa36d14550057eda30492738cedca13b13bf3a9889eb", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "0dc332165fa80b5b865eaa36d14550057eda30492738cedca13b13bf3a9889eb", kill_on_drop: false }` [INFO] [stdout] 0dc332165fa80b5b865eaa36d14550057eda30492738cedca13b13bf3a9889eb [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-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:cf8efcab8866f2cf4285301c7418e2f4f2a9b088c91ba69c40d5b659f81557f7" "/opt/rustwide/cargo-home/bin/cargo" "+4797991aa2efb6d658150f10425b3f3b5d10eceb" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 86ba94580c28f7860ae450a6a94fcc92da03d6a1ffd22c4df9e45a29c152e441 [INFO] running `Command { std: "docker" "start" "-a" "86ba94580c28f7860ae450a6a94fcc92da03d6a1ffd22c4df9e45a29c152e441", kill_on_drop: false }` [INFO] [stderr] Compiling proc-macro2 v1.0.87 [INFO] [stderr] Compiling unicode-ident v1.0.13 [INFO] [stderr] Compiling libc v0.2.159 [INFO] [stderr] Compiling autocfg v1.4.0 [INFO] [stderr] Checking byteorder v1.5.0 [INFO] [stderr] Compiling libm v0.2.8 [INFO] [stderr] Compiling crossbeam-utils v0.8.20 [INFO] [stderr] Checking either v1.13.0 [INFO] [stderr] Compiling rayon-core v1.12.1 [INFO] [stderr] Checking bytemuck v1.21.0 [INFO] [stderr] Compiling version_check v0.9.5 [INFO] [stderr] Compiling once_cell v1.20.2 [INFO] [stderr] Compiling target-lexicon v0.12.16 [INFO] [stderr] Compiling thiserror v1.0.65 [INFO] [stderr] Checking hashbrown v0.15.2 [INFO] [stderr] Compiling nano-gemm-codegen v0.1.0 [INFO] [stderr] Checking allocator-api2 v0.2.18 [INFO] [stderr] Checking reborrow v0.5.5 [INFO] [stderr] Compiling heck v0.5.0 [INFO] [stderr] Checking rawpointer v0.2.1 [INFO] [stderr] Compiling paste v1.0.15 [INFO] [stderr] Checking raw-cpuid v10.7.0 [INFO] [stderr] Checking unindent v0.2.3 [INFO] [stderr] Checking dyn-stack v0.10.0 [INFO] [stderr] Compiling ahash v0.8.11 [INFO] [stderr] Checking smallvec v1.13.2 [INFO] [stderr] Compiling indoc v2.0.5 [INFO] [stderr] Compiling ucd-trie v0.1.7 [INFO] [stderr] Compiling memchr v2.7.4 [INFO] [stderr] Compiling seq-macro v0.3.5 [INFO] [stderr] Compiling num-traits v0.2.19 [INFO] [stderr] Compiling memoffset v0.9.1 [INFO] [stderr] Compiling matrixmultiply v0.3.9 [INFO] [stderr] Checking nano-gemm-core v0.1.0 [INFO] [stderr] Checking itertools v0.10.5 [INFO] [stderr] Checking itertools v0.11.0 [INFO] [stderr] Compiling proc-macro-error-attr v1.0.4 [INFO] [stderr] Compiling nano-gemm-f64 v0.1.0 [INFO] [stderr] Compiling pyo3-build-config v0.22.6 [INFO] [stderr] Compiling nano-gemm-f32 v0.1.0 [INFO] [stderr] Compiling nano-gemm-c64 v0.1.0 [INFO] [stderr] Compiling nano-gemm-c32 v0.1.0 [INFO] [stderr] Compiling quote v1.0.37 [INFO] [stderr] Checking unicode-xid v0.2.6 [INFO] [stderr] Checking getrandom v0.2.15 [INFO] [stderr] Checking unicode-properties v0.1.3 [INFO] [stderr] Compiling rustversion v1.0.17 [INFO] [stderr] Checking crossbeam-epoch v0.9.18 [INFO] [stderr] Compiling syn v1.0.109 [INFO] [stderr] Checking oq3_lexer v0.7.0 [INFO] [stderr] Checking is-terminal v0.4.13 [INFO] [stderr] Compiling syn v2.0.79 [INFO] [stderr] Compiling proc-macro-error v1.0.4 [INFO] [stderr] Checking rand_core v0.6.4 [INFO] [stderr] Compiling ahash v0.7.8 [INFO] [stderr] Checking itertools v0.13.0 [INFO] [stderr] Checking concolor-query v0.3.3 [INFO] [stderr] Compiling xshell-macros v0.2.6 [INFO] [stderr] Checking countme v3.0.1 [INFO] [stderr] Checking drop_bomb v0.1.5 [INFO] [stderr] Checking text-size v1.1.1 [INFO] [stderr] Checking ra_ap_limit v0.0.188 [INFO] [stderr] Checking crossbeam-deque v0.8.5 [INFO] [stderr] Compiling serde v1.0.210 [INFO] [stderr] Checking rand_pcg v0.3.1 [INFO] [stderr] Checking oq3_parser v0.7.0 [INFO] [stderr] Checking concolor v0.1.1 [INFO] [stderr] Checking aho-corasick v1.1.3 [INFO] [stderr] Checking xshell v0.2.6 [INFO] [stderr] Checking smol_str v0.2.2 [INFO] [stderr] Checking triomphe v0.1.11 [INFO] [stderr] Checking regex-syntax v0.8.5 [INFO] [stderr] Checking unicode-width v0.1.14 [INFO] [stderr] Checking coe-rs v0.1.2 [INFO] [stderr] Checking matrixcompare-core v0.1.0 [INFO] [stderr] Checking cov-mark v2.0.0 [INFO] [stderr] Checking yansi v0.5.1 [INFO] [stderr] Checking dbgf v0.1.2 [INFO] [stderr] Checking lazy_static v1.5.0 [INFO] [stderr] Checking hashbrown v0.12.3 [INFO] [stderr] Checking ariadne v0.3.0 [INFO] [stderr] Checking num-integer v0.1.46 [INFO] [stderr] Checking approx v0.4.0 [INFO] [stderr] Checking rayon v1.10.0 [INFO] [stderr] Checking matrixcompare v0.3.0 [INFO] [stderr] Compiling pyo3-macros-backend v0.22.6 [INFO] [stderr] Compiling pyo3-ffi v0.22.6 [INFO] [stderr] Compiling pyo3 v0.22.6 [INFO] [stderr] Checking num-bigint v0.4.6 [INFO] [stderr] Compiling boolenum v0.1.0 [INFO] [stderr] Checking regex-automata v0.4.8 [INFO] [stderr] Checking indexmap v2.7.0 [INFO] [stderr] Checking rayon-cond v0.3.0 [INFO] [stderr] Compiling zerocopy-derive v0.7.35 [INFO] [stderr] Compiling thiserror-impl v1.0.65 [INFO] [stderr] Compiling pulp-macro v0.1.1 [INFO] [stderr] Compiling equator-macro v0.2.1 [INFO] [stderr] Compiling serde_derive v1.0.210 [INFO] [stderr] Compiling equator-macro v0.4.1 [INFO] [stderr] Checking petgraph v0.6.5 [INFO] [stderr] Checking priority-queue v2.1.1 [INFO] [stderr] Checking equator v0.2.2 [INFO] [stderr] Checking regex v1.11.0 [INFO] [stderr] Checking equator v0.4.1 [INFO] [stderr] Checking zerocopy v0.7.35 [INFO] [stderr] Compiling pest v2.7.13 [INFO] [stderr] Checking ppv-lite86 v0.2.20 [INFO] [stderr] Checking hashbrown v0.14.5 [INFO] [stderr] Checking rand_chacha v0.3.1 [INFO] [stderr] Checking rand v0.8.5 [INFO] [stderr] Checking rowan v0.15.15 [INFO] [stderr] Compiling pest_meta v2.7.13 [INFO] [stderr] Checking oq3_syntax v0.7.0 [INFO] [stderr] Checking num-complex v0.4.6 [INFO] [stderr] Checking rand_distr v0.4.3 [INFO] [stderr] Checking rustiq-core v0.0.10 [INFO] [stderr] Compiling pyo3-macros v0.22.6 [INFO] [stderr] Compiling pest_generator v2.7.13 [INFO] [stderr] Checking approx v0.5.1 [INFO] [stderr] Checking pulp v0.18.22 [INFO] [stderr] Checking ndarray v0.15.6 [INFO] [stderr] Checking oq3_source_file v0.7.0 [INFO] [stderr] Checking oq3_semantics v0.7.0 [INFO] [stderr] Compiling pest_derive v2.7.13 [INFO] [stderr] Checking py_literal v0.4.0 [INFO] [stderr] Checking npyz v0.8.3 [INFO] [stderr] Checking qiskit-qasm3 v2.0.0 (/opt/rustwide/workdir/crates/qasm3) [INFO] [stderr] Checking gemm-common v0.18.0 [INFO] [stderr] Checking faer-entity v0.19.2 [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/qasm3/src/error.rs:15:1 [INFO] [stdout] | [INFO] [stdout] 15 | import_exception!(qiskit.qasm3.exceptions, QASM3ImporterError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/qasm3/src/error.rs:15:1 [INFO] [stdout] | [INFO] [stdout] 15 | import_exception!(qiskit.qasm3.exceptions, QASM3ImporterError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/qasm3/src/error.rs:15:1 [INFO] [stdout] | [INFO] [stdout] 15 | import_exception!(qiskit.qasm3.exceptions, QASM3ImporterError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/qasm3/src/error.rs:15:1 [INFO] [stdout] | [INFO] [stdout] 15 | import_exception!(qiskit.qasm3.exceptions, QASM3ImporterError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking gemm-c32 v0.18.0 [INFO] [stderr] Checking gemm-f32 v0.18.0 [INFO] [stderr] Checking gemm-c64 v0.18.0 [INFO] [stderr] Checking gemm-f64 v0.18.0 [INFO] [stderr] Checking numpy v0.22.1 [INFO] [stderr] Checking rustworkx-core v0.15.1 [INFO] [stderr] Checking ndarray_einsum_beta v0.7.0 [INFO] [stderr] Checking gemm v0.18.0 [INFO] [stderr] Checking qiskit-circuit v2.0.0 (/opt/rustwide/workdir/crates/circuit) [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/circuit/src/circuit_data.rs:40:1 [INFO] [stdout] | [INFO] [stdout] 40 | import_exception!(qiskit.circuit.exceptions, CircuitError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/circuit/src/circuit_data.rs:40:1 [INFO] [stdout] | [INFO] [stdout] 40 | import_exception!(qiskit.circuit.exceptions, CircuitError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/circuit/src/error.rs:15:1 [INFO] [stdout] | [INFO] [stdout] 15 | import_exception!(qiskit.dagcircuit.exceptions, DAGCircuitError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/circuit/src/error.rs:15:1 [INFO] [stdout] | [INFO] [stdout] 15 | import_exception!(qiskit.dagcircuit.exceptions, DAGCircuitError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/circuit/src/error.rs:16:1 [INFO] [stdout] | [INFO] [stdout] 16 | import_exception!(qiskit.dagcircuit.exceptions, DAGDependencyError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/circuit/src/error.rs:16:1 [INFO] [stdout] | [INFO] [stdout] 16 | import_exception!(qiskit.dagcircuit.exceptions, DAGDependencyError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/circuit/src/parameter_table.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | import_exception!(qiskit.circuit, CircuitError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/circuit/src/parameter_table.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | import_exception!(qiskit.circuit, CircuitError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/circuit/src/circuit_data.rs:40:1 [INFO] [stdout] | [INFO] [stdout] 40 | import_exception!(qiskit.circuit.exceptions, CircuitError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/circuit/src/circuit_data.rs:40:1 [INFO] [stdout] | [INFO] [stdout] 40 | import_exception!(qiskit.circuit.exceptions, CircuitError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/circuit/src/error.rs:15:1 [INFO] [stdout] | [INFO] [stdout] 15 | import_exception!(qiskit.dagcircuit.exceptions, DAGCircuitError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/circuit/src/error.rs:15:1 [INFO] [stdout] | [INFO] [stdout] 15 | import_exception!(qiskit.dagcircuit.exceptions, DAGCircuitError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/circuit/src/error.rs:16:1 [INFO] [stdout] | [INFO] [stdout] 16 | import_exception!(qiskit.dagcircuit.exceptions, DAGDependencyError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/circuit/src/error.rs:16:1 [INFO] [stdout] | [INFO] [stdout] 16 | import_exception!(qiskit.dagcircuit.exceptions, DAGDependencyError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/circuit/src/parameter_table.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | import_exception!(qiskit.circuit, CircuitError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/circuit/src/parameter_table.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | import_exception!(qiskit.circuit, CircuitError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/circuit/src/circuit_instruction.rs:89:29 [INFO] [stdout] | [INFO] [stdout] 89 | pub fn default_unit(py: Python) -> &Bound { [INFO] [stdout] | ^^^^^^ ---------------- [INFO] [stdout] | | || [INFO] [stdout] | | |the lifetimes get resolved as `'_` [INFO] [stdout] | | the lifetimes get resolved as `'_` [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 89 | pub fn default_unit(py: Python<'_>) -> &Bound<'_, PyString> { [INFO] [stdout] | ++++ +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/circuit/src/dag_circuit.rs:5169:17 [INFO] [stdout] | [INFO] [stdout] 5169 | fn sort_key(&self, node: NodeIndex) -> SortKeyType { [INFO] [stdout] | ^^^^^ ----------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 5169 | fn sort_key(&self, node: NodeIndex) -> SortKeyType<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static [INFO] [stdout] --> crates/circuit/src/imports.rs:264:15 [INFO] [stdout] | [INFO] [stdout] 264 | match STDGATE_PYTHON_GATES.get_mut() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: `#[warn(static_mut_refs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a shared reference to mutable static [INFO] [stdout] --> crates/circuit/src/imports.rs:268:17 [INFO] [stdout] | [INFO] [stdout] 268 | STDGATE_PYTHON_GATES.set(py, array).unwrap(); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ shared reference to mutable static [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: shared references to mutable statics are dangerous; it's undefined behavior if the static is mutated or if a mutable reference is created for it while the shared reference lives [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static [INFO] [stdout] --> crates/circuit/src/imports.rs:269:17 [INFO] [stdout] | [INFO] [stdout] 269 | STDGATE_PYTHON_GATES.get_mut().unwrap() [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a shared reference to mutable static [INFO] [stdout] --> crates/circuit/src/imports.rs:282:18 [INFO] [stdout] | [INFO] [stdout] 282 | unsafe { STDGATE_PYTHON_GATES.get_or_init(py, || std::array::from_fn(|_| None)) }; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ shared reference to mutable static [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: shared references to mutable statics are dangerous; it's undefined behavior if the static is mutated or if a mutable reference is created for it while the shared reference lives [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/circuit/src/packed_instruction.rs:192:17 [INFO] [stdout] | [INFO] [stdout] 192 | pub fn view(&self) -> OperationRef { [INFO] [stdout] | ^^^^^ ------------ the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 192 | pub fn view(&self) -> OperationRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking qiskit-qasm2 v2.0.0 (/opt/rustwide/workdir/crates/qasm2) [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/circuit/src/circuit_instruction.rs:89:29 [INFO] [stdout] | [INFO] [stdout] 89 | pub fn default_unit(py: Python) -> &Bound { [INFO] [stdout] | ^^^^^^ ---------------- [INFO] [stdout] | | || [INFO] [stdout] | | |the lifetimes get resolved as `'_` [INFO] [stdout] | | the lifetimes get resolved as `'_` [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 89 | pub fn default_unit(py: Python<'_>) -> &Bound<'_, PyString> { [INFO] [stdout] | ++++ +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/circuit/src/dag_circuit.rs:5169:17 [INFO] [stdout] | [INFO] [stdout] 5169 | fn sort_key(&self, node: NodeIndex) -> SortKeyType { [INFO] [stdout] | ^^^^^ ----------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 5169 | fn sort_key(&self, node: NodeIndex) -> SortKeyType<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static [INFO] [stdout] --> crates/circuit/src/imports.rs:264:15 [INFO] [stdout] | [INFO] [stdout] 264 | match STDGATE_PYTHON_GATES.get_mut() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] = note: `#[warn(static_mut_refs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a shared reference to mutable static [INFO] [stdout] --> crates/circuit/src/imports.rs:268:17 [INFO] [stdout] | [INFO] [stdout] 268 | STDGATE_PYTHON_GATES.set(py, array).unwrap(); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ shared reference to mutable static [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: shared references to mutable statics are dangerous; it's undefined behavior if the static is mutated or if a mutable reference is created for it while the shared reference lives [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a mutable reference to mutable static [INFO] [stdout] --> crates/circuit/src/imports.rs:269:17 [INFO] [stdout] | [INFO] [stdout] 269 | STDGATE_PYTHON_GATES.get_mut().unwrap() [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: creating a shared reference to mutable static [INFO] [stdout] --> crates/circuit/src/imports.rs:282:18 [INFO] [stdout] | [INFO] [stdout] 282 | unsafe { STDGATE_PYTHON_GATES.get_or_init(py, || std::array::from_fn(|_| None)) }; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ shared reference to mutable static [INFO] [stdout] | [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: shared references to mutable statics are dangerous; it's undefined behavior if the static is mutated or if a mutable reference is created for it while the shared reference lives [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/circuit/src/packed_instruction.rs:192:17 [INFO] [stdout] | [INFO] [stdout] 192 | pub fn view(&self) -> OperationRef { [INFO] [stdout] | ^^^^^ ------------ the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 192 | pub fn view(&self) -> OperationRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/qasm2/src/error.rs:82:1 [INFO] [stdout] | [INFO] [stdout] 82 | import_exception!(qiskit.qasm2.exceptions, QASM2ParseError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/qasm2/src/error.rs:82:1 [INFO] [stdout] | [INFO] [stdout] 82 | import_exception!(qiskit.qasm2.exceptions, QASM2ParseError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/qasm2/src/error.rs:82:1 [INFO] [stdout] | [INFO] [stdout] 82 | import_exception!(qiskit.qasm2.exceptions, QASM2ParseError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/qasm2/src/error.rs:82:1 [INFO] [stdout] | [INFO] [stdout] 82 | import_exception!(qiskit.qasm2.exceptions, QASM2ParseError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking nano-gemm v0.1.2 [INFO] [stderr] Checking faer v0.19.4 [INFO] [stderr] Checking faer-ext v0.2.0 [INFO] [stderr] Checking qiskit-accelerate v2.0.0 (/opt/rustwide/workdir/crates/accelerate) [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/accelerate/src/lib.rs:82:1 [INFO] [stdout] | [INFO] [stdout] 82 | import_exception!(qiskit.exceptions, QiskitError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/accelerate/src/lib.rs:82:1 [INFO] [stdout] | [INFO] [stdout] 82 | import_exception!(qiskit.exceptions, QiskitError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/accelerate/src/lib.rs:83:1 [INFO] [stdout] | [INFO] [stdout] 83 | import_exception!(qiskit.circuit.exceptions, CircuitError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/accelerate/src/lib.rs:83:1 [INFO] [stdout] | [INFO] [stdout] 83 | import_exception!(qiskit.circuit.exceptions, CircuitError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/accelerate/src/equivalence.rs:47:5 [INFO] [stdout] | [INFO] [stdout] 47 | import_exception_bound! {qiskit.circuit.exceptions, CircuitError} [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `import_exception_bound` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `import_exception_bound` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `import_exception_bound` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/accelerate/src/target_transpiler/mod.rs:48:5 [INFO] [stdout] | [INFO] [stdout] 48 | import_exception_bound! {qiskit.exceptions, QiskitError} [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `import_exception_bound` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `import_exception_bound` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `import_exception_bound` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/accelerate/src/target_transpiler/mod.rs:49:5 [INFO] [stdout] | [INFO] [stdout] 49 | import_exception_bound! {qiskit.transpiler.exceptions, TranspilerError} [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `import_exception_bound` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `import_exception_bound` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `import_exception_bound` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/accelerate/src/lib.rs:82:1 [INFO] [stdout] | [INFO] [stdout] 82 | import_exception!(qiskit.exceptions, QiskitError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/accelerate/src/lib.rs:82:1 [INFO] [stdout] | [INFO] [stdout] 82 | import_exception!(qiskit.exceptions, QiskitError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/accelerate/src/lib.rs:83:1 [INFO] [stdout] | [INFO] [stdout] 83 | import_exception!(qiskit.circuit.exceptions, CircuitError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/accelerate/src/lib.rs:83:1 [INFO] [stdout] | [INFO] [stdout] 83 | import_exception!(qiskit.circuit.exceptions, CircuitError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a 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 `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/accelerate/src/equivalence.rs:47:5 [INFO] [stdout] | [INFO] [stdout] 47 | import_exception_bound! {qiskit.circuit.exceptions, CircuitError} [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `import_exception_bound` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `import_exception_bound` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `import_exception_bound` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/accelerate/src/target_transpiler/mod.rs:48:5 [INFO] [stdout] | [INFO] [stdout] 48 | import_exception_bound! {qiskit.exceptions, QiskitError} [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `import_exception_bound` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `import_exception_bound` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `import_exception_bound` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> crates/accelerate/src/target_transpiler/mod.rs:49:5 [INFO] [stdout] | [INFO] [stdout] 49 | import_exception_bound! {qiskit.transpiler.exceptions, TranspilerError} [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cache_pygates` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `import_exception_bound` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `import_exception_bound` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `import_exception_bound` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/accelerate/src/circuit_library/iqp.rs:33:19 [INFO] [stdout] | [INFO] [stdout] 33 | interactions: ArrayView2, [INFO] [stdout] | ^^^^^^^^^^^^^^^ this lifetime flows to the output [INFO] [stdout] 34 | ) -> impl Iterator, SmallVec<[Qubit; 2]>)> + '_ { [INFO] [stdout] | -- the lifetime gets resolved as `'_` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: one option is to consistently use `'_` [INFO] [stdout] | [INFO] [stdout] 33 | interactions: ArrayView2<'_, i64>, [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/accelerate/src/circuit_library/parameter_ledger.rs:137:34 [INFO] [stdout] | [INFO] [stdout] 137 | pub(super) fn get_parameters(&self, kind: LayerType, layer: usize) -> LayerParameters { [INFO] [stdout] | ^^^^^ this lifetime flows to the output --------------- the lifetime gets resolved as `'_` [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 137 | pub(super) fn get_parameters(&self, kind: LayerType, layer: usize) -> LayerParameters<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/accelerate/src/circuit_library/iqp.rs:33:19 [INFO] [stdout] | [INFO] [stdout] 33 | interactions: ArrayView2, [INFO] [stdout] | ^^^^^^^^^^^^^^^ this lifetime flows to the output [INFO] [stdout] 34 | ) -> impl Iterator, SmallVec<[Qubit; 2]>)> + '_ { [INFO] [stdout] | -- the lifetime gets resolved as `'_` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: one option is to consistently use `'_` [INFO] [stdout] | [INFO] [stdout] 33 | interactions: ArrayView2<'_, i64>, [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/accelerate/src/circuit_library/parameter_ledger.rs:137:34 [INFO] [stdout] | [INFO] [stdout] 137 | pub(super) fn get_parameters(&self, kind: LayerType, layer: usize) -> LayerParameters { [INFO] [stdout] | ^^^^^ this lifetime flows to the output --------------- the lifetime gets resolved as `'_` [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 137 | pub(super) fn get_parameters(&self, kind: LayerType, layer: usize) -> LayerParameters<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/accelerate/src/sparse_observable.rs:986:17 [INFO] [stdout] | [INFO] [stdout] 986 | pub fn term(&self, index: usize) -> SparseTermView { [INFO] [stdout] | ^^^^^ -------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 986 | pub fn term(&self, index: usize) -> SparseTermView<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/accelerate/src/sparse_observable.rs:2574:20 [INFO] [stdout] | [INFO] [stdout] 2574 | fn from(value: &mut SparseObservable) -> IterMut { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ ------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 2574 | fn from(value: &mut SparseObservable) -> IterMut<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/accelerate/src/sparse_observable.rs:2830:17 [INFO] [stdout] | [INFO] [stdout] 2830 | pub fn view(&self) -> SparseTermView { [INFO] [stdout] | ^^^^^ -------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 2830 | pub fn view(&self) -> SparseTermView<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/accelerate/src/sparse_pauli_op.rs:199:17 [INFO] [stdout] | [INFO] [stdout] 199 | fn as_array(&self) -> ZXPaulisView { [INFO] [stdout] | ^^^^^ ------------ the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 199 | fn as_array(&self) -> ZXPaulisView<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/accelerate/src/synthesis/clifford/greedy_synthesis.rs:110:32 [INFO] [stdout] | [INFO] [stdout] 110 | pub(crate) fn new(tableau: ArrayView2) -> Result, String> { [INFO] [stdout] | ^^^^^^^^^^^^^^^^ this lifetime flows to the output -- the lifetime gets resolved as `'_` [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'_` [INFO] [stdout] | [INFO] [stdout] 110 | pub(crate) fn new(tableau: ArrayView2<'_, bool>) -> Result, String> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/accelerate/src/target_transpiler/nullable_index_map.rs:164:17 [INFO] [stdout] | [INFO] [stdout] 164 | pub fn iter(&self) -> Iter { [INFO] [stdout] | ^^^^^ ---------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 164 | pub fn iter(&self) -> Iter<'_, K, V> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/accelerate/src/target_transpiler/nullable_index_map.rs:172:17 [INFO] [stdout] | [INFO] [stdout] 172 | pub fn keys(&self) -> Keys { [INFO] [stdout] | ^^^^^ ---------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 172 | pub fn keys(&self) -> Keys<'_, K, V> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/accelerate/src/target_transpiler/nullable_index_map.rs:180:19 [INFO] [stdout] | [INFO] [stdout] 180 | pub fn values(&self) -> Values { [INFO] [stdout] | ^^^^^ ------------ the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 180 | pub fn values(&self) -> Values<'_, K, V> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/accelerate/src/sparse_observable.rs:986:17 [INFO] [stdout] | [INFO] [stdout] 986 | pub fn term(&self, index: usize) -> SparseTermView { [INFO] [stdout] | ^^^^^ -------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 986 | pub fn term(&self, index: usize) -> SparseTermView<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/accelerate/src/sparse_observable.rs:2574:20 [INFO] [stdout] | [INFO] [stdout] 2574 | fn from(value: &mut SparseObservable) -> IterMut { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ ------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 2574 | fn from(value: &mut SparseObservable) -> IterMut<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/accelerate/src/sparse_observable.rs:2830:17 [INFO] [stdout] | [INFO] [stdout] 2830 | pub fn view(&self) -> SparseTermView { [INFO] [stdout] | ^^^^^ -------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 2830 | pub fn view(&self) -> SparseTermView<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/accelerate/src/sparse_pauli_op.rs:199:17 [INFO] [stdout] | [INFO] [stdout] 199 | fn as_array(&self) -> ZXPaulisView { [INFO] [stdout] | ^^^^^ ------------ the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 199 | fn as_array(&self) -> ZXPaulisView<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/accelerate/src/synthesis/clifford/greedy_synthesis.rs:110:32 [INFO] [stdout] | [INFO] [stdout] 110 | pub(crate) fn new(tableau: ArrayView2) -> Result, String> { [INFO] [stdout] | ^^^^^^^^^^^^^^^^ this lifetime flows to the output -- the lifetime gets resolved as `'_` [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'_` [INFO] [stdout] | [INFO] [stdout] 110 | pub(crate) fn new(tableau: ArrayView2<'_, bool>) -> Result, String> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/accelerate/src/target_transpiler/nullable_index_map.rs:164:17 [INFO] [stdout] | [INFO] [stdout] 164 | pub fn iter(&self) -> Iter { [INFO] [stdout] | ^^^^^ ---------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 164 | pub fn iter(&self) -> Iter<'_, K, V> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/accelerate/src/target_transpiler/nullable_index_map.rs:172:17 [INFO] [stdout] | [INFO] [stdout] 172 | pub fn keys(&self) -> Keys { [INFO] [stdout] | ^^^^^ ---------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 172 | pub fn keys(&self) -> Keys<'_, K, V> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> crates/accelerate/src/target_transpiler/nullable_index_map.rs:180:19 [INFO] [stdout] | [INFO] [stdout] 180 | pub fn values(&self) -> Values { [INFO] [stdout] | ^^^^^ ------------ the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 180 | pub fn values(&self) -> Values<'_, K, V> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking qiskit-pyext v2.0.0 (/opt/rustwide/workdir/crates/pyext) [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 1m 37s [INFO] running `Command { std: "docker" "inspect" "86ba94580c28f7860ae450a6a94fcc92da03d6a1ffd22c4df9e45a29c152e441", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "86ba94580c28f7860ae450a6a94fcc92da03d6a1ffd22c4df9e45a29c152e441", kill_on_drop: false }` [INFO] [stdout] 86ba94580c28f7860ae450a6a94fcc92da03d6a1ffd22c4df9e45a29c152e441