-
-
Notifications
You must be signed in to change notification settings - Fork 99
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
Nextest doesn't work in workspace where Cargo.toml of workspace is not hierarchically higher than crates #1684
Comments
Thank you! I've never seen this before to be honest. Do you have a reference in the Cargo documentation for it? |
Hi @sunshowers , I'm sorry but I didn't understand what reference do you want me to provide? |
Thanks. I had another look at your repro, and to be honest I didn't know that you could use This would have to be addressed in the underlying guppy library (also maintained by myself), https://github.com/guppy-rs/guppy. I don't plan to fix this myself but a patch would be welcome. |
I don't plan to work on this, but a patch would be welcome. |
I checked the error message, if do not restrict manifest path must within workspace path, nextest can run tests at MinimalRepo. If you are sure this restriction can be bypass optionally, I can try provide patch to Guppy and Nextest. |
Patch is ready now, for guppy repository, please review |
In guppy PR #331 now |
Output
File structures
MinimalRepro repository
What I think the issue is
I believe that nextest assumes that the workspace Cargo.toml will always be in a parent folder of the crates the workspace contains.
The text was updated successfully, but these errors were encountered: