-
-
Notifications
You must be signed in to change notification settings - Fork 174
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
v0.9 segfaults during tests #264
Comments
Ah cripes. You should be able to revert to the old behaviour by adding |
👍 can confirm |
[GitHub] See also xd009642/tarpaulin#264. Signed-off-by: Kristofer Rye <kristofer.rye@gmail.com>
[GitHub] See also xd009642/tarpaulin#264. Signed-off-by: Kristofer Rye <kristofer.rye@gmail.com>
See also xd009642/tarpaulin#264. Should probably revert this once tarpaulin is fixed.
This may be fixed in the 0.9.1 release which is in the process of being built and pushed to crates.io via github actions |
It appears that version 0.9.1 has been released, which might fix the execution in parallel causing segmentation faults. See xd009642/tarpaulin#264 for the discussion about this issue. I will test this and see if it works! Signed-off-by: Kristofer Rye <kristofer.rye@gmail.com>
It seems to no longer be needed, per the new release of tarpaulin that seems to resolve xd009642/tarpaulin#264. Signed-off-by: Kristofer Rye <kristofer.rye@gmail.com>
It seems to no longer be needed, per the new release of tarpaulin that seems to resolve xd009642/tarpaulin#264. Signed-off-by: Kristofer Rye <kristofer.rye@gmail.com>
Can confirm it's fixed on my end :) happy to close if no one else has objections |
Closing any new segfaults etc open a new issue as this one has already covered two causes no need to grow it further :) |
After the 0.9 release tarpaulin started to segfault when running tests:
The text was updated successfully, but these errors were encountered: