-
Notifications
You must be signed in to change notification settings - Fork 9
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
Support workspace inheritance #74
Comments
Signed-off-by: Mark Van de Vyver <[email protected]>
test-feature
test-feature
Note to self to investigate possible workaround: Cargo virtual manifests do not support the |
Signed-off-by: Mark Van de Vyver <[email protected]>
|
test-feature
Ah, nah, the direct reason for this error itself could be due to a failure to parse the edition (fixed by #92). However, as far as I can see #72, even if that error is fixed, it is likely that another error will be shown because of the workspace inheritance. |
I've encountered this issue while implementing a infinyon/fluvio plugin-style integration test harness for Minitest, PR tikv/minitrace-rust/pull/127.
I have now reproduced the issue in a
test-virtual
project that will, hopefully, land here via PR #72.The
test-virtual
example shows how to setup macrotest with a generic (non-libtest
) test harness, and allows macrotest users to compare this plugin-style integration test suite with the default Rustlibtest
test harness.At the moment the
test-virtual
project returns this error:I've banged my head on both projects but can't seem to figure out where the mismatch is occuring.
Appreciate any help or insights you can share.
The text was updated successfully, but these errors were encountered: