You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
repository link (if public, optional): icicle-emu/icicle-python#11 (make sure to check out 21531db2e0f87a729ccae5738afc4bbff1be029a)
Bug description
Because of complex reasons it is impossible to execute cargo test in a project that links to pyo3 (specifically with the extension-module feature). As a workaround I put a [workspace] in my Cargo.toml and have a separate tests package to test my rust code. To run the tests I do cargo test --package tests, which works fine (for now I have only an example test, because I ran into this issue).
Unfortunately when clicking the 'Run test' button on the tests/tests.rs file (which is part of the tests package member of the workspace) in VSCode, rust-analyzer passes --package icicle-python (the root package).
The text was updated successfully, but these errors were encountered:
Requested information
rust-analyzer version: rust-analyzer version: 0.3.2228-standalone (fa4a40b 2024-12-22)
rustc version: rustc 1.81.0 (eeb90cda1 2024-09-04)
editor or extension: VSCode
relevant settings: N/A (default, didn't change anything)
repository link (if public, optional): icicle-emu/icicle-python#11 (make sure to check out 21531db2e0f87a729ccae5738afc4bbff1be029a)
Bug description
Because of complex reasons it is impossible to execute
cargo test
in a project that links to pyo3 (specifically with theextension-module
feature). As a workaround I put a[workspace]
in myCargo.toml
and have a separatetests
package to test my rust code. To run the tests I docargo test --package tests
, which works fine (for now I have only anexample
test, because I ran into this issue).Unfortunately when clicking the 'Run test' button on the
tests/tests.rs
file (which is part of thetests
package member of the workspace) in VSCode, rust-analyzer passes--package icicle-python
(the root package).The text was updated successfully, but these errors were encountered: