-
Notifications
You must be signed in to change notification settings - Fork 9
Parallel tests fail in workspace project #71
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
Comments
taqtiqa-mark
added a commit
to taqtiqa-mark/macrotest
that referenced
this issue
Mar 28, 2022
This initial commit contains the state of play immediately after add the example crates: - test-project - test-procmacro-project Other than setting up the workspace references no changes to the example crates have been made. The integration test harness has not yet been implemented. Signed-off-by: Mark Van de Vyver <[email protected]>
Workaround for the cargo test -- --test-threads=1 However, this does not workaround the issue in the |
taqtiqa-mark
added a commit
to taqtiqa-mark/macrotest
that referenced
this issue
Mar 10, 2024
This initial commit contains the state of play immediately after add the example crates: - test-project - test-procmacro-project Other than setting up the workspace references no changes to the example crates have been made. The integration test harness has not yet been implemented. Signed-off-by: Mark Van de Vyver <[email protected]>
This is due to the crate that defining macro is "wrkspc-test" but you are importing Closing as this doesn't seem to macrotest bug. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thank you for the effort you have put into making macrotest, and for making it open source.
I ran into this issue in the course of trying to isolate what appears to be unexpected behavior.
PR #72 proposes to add a workspace project example, and this error can be observed by checking out the first commit in the PR.
Should show these two results for
parallel_1
andparallel_2
test cases:The text was updated successfully, but these errors were encountered: