Is anyone else having problems running tests from the VSCode test explorer? #4030
Replies: 3 comments 4 replies
-
|
No problems here. Maybe try adding |
Beta Was this translation helpful? Give feedback.
-
|
Hmm ... that doesn't give any extra output. I also tried it from the shell and don't get anything extra: pyo3@90b687936b37:/workspaces/pyo3$ echo $PYO3_PRINT_CONFIG
1
pyo3@90b687936b37:/workspaces/pyo3$ cargo test test_bytes
Compiling pyo3 v0.21.0 (/workspaces/pyo3)
Finished test [unoptimized + debuginfo] target(s) in 11.27s
Running unittests src/lib.rs (target/debug/deps/pyo3-a16add32573a8980)
running 5 tests
test types::bytes::tests::test_bytes_new_with ... ok
test buffer::tests::test_bytes_buffer ... ok
test types::bytes::tests::test_bytes_new_with_error ... ok
test types::bytes::tests::test_bytes_index ... ok
test types::bytes::tests::test_bytes_new_with_zero_initialised ... ok
test result: ok. 5 passed; 0 failed; 0 ignored; 0 measured; 630 filtered out; finished in 0.03s |
Beta Was this translation helpful? Give feedback.
-
|
Bizarre. It definitely works on my machine: |
Beta Was this translation helpful? Give feedback.
-
|
Yes that is really weird. I'd like to say THANKS for the awesome support on discussing this, it's really nice. My offer to pay it back is to update the contributing docs if we find anything that could be clearer for others, although right now I'm tending towards it being an issue with rust-analyzer and the experimental support for the test explorer ... Running the exact same command as you did I got: pyo3@81421337f171:/workspaces/pyo3$PYO3_PRINT_CONFIG=1 cargo test test_bytes
Compiling proc-macro2 v1.0.79
Compiling pyo3-ffi v0.21.0 (/workspaces/pyo3/pyo3-ffi)
error: failed to run custom build command for `pyo3-ffi v0.21.0 (/workspaces/pyo3/pyo3-ffi)`
Caused by:
process didn't exit successfully: `/workspaces/pyo3/target/debug/build/pyo3-ffi-e9e6d905bfdb2b93/build-script-build` (exit status: 101)
--- stdout
cargo:rerun-if-env-changed=PYO3_CROSS
cargo:rerun-if-env-changed=PYO3_CROSS_LIB_DIR
cargo:rerun-if-env-changed=PYO3_CROSS_PYTHON_VERSION
cargo:rerun-if-env-changed=PYO3_CROSS_PYTHON_IMPLEMENTATION
cargo:rerun-if-env-changed=PYO3_PRINT_CONFIG
-- PYO3_PRINT_CONFIG=1 is set, printing configuration and halting compile --
implementation=CPython
version=3.12
shared=true
abi3=false
lib_name=python3.12
lib_dir=/usr/lib64
executable=/usr/bin/python
pointer_width=64
build_flags=
suppress_build_script_link_lines=false
note: unset the PYO3_PRINT_CONFIG environment variable and retry to compile with the above config
warning: build failed, waiting for other jobs to finish...I also get the same if I export PYO3_PRINT_CONFIG and then run the test separately but I DON'T get the output if running the test from test explorer even after the export. I've tried adding: "rust-analyzer.runnables.extraEnv": {
"PYO3_PRINT_CONFIG": "1"
},to settings.json with no effect. I've also tried adding: "rust-analyzer.cargo.extraEnv": {
"PYO3_PRINT_CONFIG": "1"
}and get similar output immediately in Output - Rust Analyzer Language Server. In that case: So it is obviously reading the variable in that case and using the build.rs files (but ignoring the export-ed env variable) what does your settings.json look like? Without the print_config variables, mine is: {
"rust-analyzer.interpret.tests": true,
"rust-analyzer.testExplorer": true,
"coverage-gutters.coverageFileNames": [
"lcov.info",
"cov.xml",
"coverage.xml"
],
"coverage-gutters.showLineCoverage": true,
"terminal.integrated.defaultProfile.linux": "bash",
"terminal.integrated.profiles.linux": {
"bash": {
"path": "/usr/bin/bash"
}
},
"editor.rulers": [
100
]
}If you hadn't said you have Test Explorer already working I'd be sure it was an issue with analyzer ... it may still be, but it looks a little more complex. Once again, thank you so much for supporting and engaging on this. I hope it will also be useful for other contributors in the future. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry to have taken a while to come back to this, I've been pretty behind on OSS the last couple of weeks. Now I see your settings, I realise I misunderstood what you meant by tests in VSCode. The little "run test" hint text works (as that delegates to "cargo test"). The green arrow does not, I get the same linker errors as you. I guess we should follow up with the rust-analyzer folks to understand what's going on there.
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks, that's a really good tip with the Run Test hint. I've been running tests via the command line. |
Beta Was this translation helpful? Give feedback.
-
|
For future reference I have raised: rust-lang/rust-analyzer#17136 |
Beta Was this translation helpful? Give feedback.
-
I'm just getting started with the pyo3 codebase and am having an issue running the tests from within VSCode.
cargo testworks fine from the command line but when I try to run the tests from within VSCode I get an error which suggests it's missing some libraries to link...Did anyone else have similar issues? I'm guessing there is a specific setup entry that I'm missing to tell rust-analyser to also link python libraries as it cannot cope with the more complex build.rs construct in pyo3 ...
If no one here has fixed this for themselves then I can work on the command line for now and raise a bug with rust-analyser.
The relevant parts of my vscode setup (devcontainer.json)
and the packages installed
(Full setup is here: https://github.com/MusicalNinjaDad/devcontainers-python-rust)
Beta Was this translation helpful? Give feedback.
All reactions