-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test_opening_simple_nft_manifest_should_return_fresh_analysis
is failing after compiling with my nix package definition
#1546
Comments
Hello @malikwirin Couple of things to consider:
But this is a side note, I don't think it would actually fix the issue.
|
Hi @hugocaillard
rustPlatform.buildRustPackage {
/* ... */
useNextest = true;
checkFlags = [
"--workspace --locked --exclude clarinet-sdk-wasm --exclude clarity-jupyter-kernel"
];
} Currently I am doing this for my setup but I could imagine upstreaming it when it follows best practices. Opening up such a Pull Request would enable more people to debug this. |
This did not work actually it should have been rust.Platform.buildRustPackage {
/* ... */
useNextest = true;
checkPhase = ''
cargo tst
'';
} So we are making progress. This time I had 174 passing tests.
It's still clarinet-cli::bin/clarinet lsp::test_opening_simple_nft_manifest_should_return_fresh_analysis which fails. What mode is the rust package build for testing normally? In my nix setup it uses release mode by default, but should I maybe use debug mode? |
test_opening_simple_nft_manifest_should_return_fresh_analysis
is failing after compiling with my nix package definition
I don't know. As suggested in my previous comment, is it possible for you to add a log?
Both seem to work on my end |
So I included a patch to get the value of manifest_location: println!("Manifest location: {:?}", manifest_location); The value is |
I am currently trying to package clarinet for NixOS like I talked about in #1515 .
I have the following package definition:
There is also a Cargo.lock file in the directory of the nix file. I can post its content if necessary.
The build phase runs successful, but the checkPhase doesn't. With the following log:
Inside the failing test
response.aggregated_diagnostics.len()
returns 0 even though it should return 1.What may cause this?
The text was updated successfully, but these errors were encountered: