-
Notifications
You must be signed in to change notification settings - Fork 13
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
Coverage error: failed to parse lock file #66
Comments
I can tell you what causes it: the new lockfile format. I think cargo-travis "just" needs to update cargo-as-a-library and it should "just work" again. In the mean time, you can commit a lockfile generated by a rust < 1.41 and it'll keep using the old, compatible lockfile format. |
I have a branch where I moved to using cargo metadata. It isn’t well tested though. If you want to try it, try to install the cargo-metadata branch of cargo-travis. |
@roblabla Do you have any updates on this issue? Is the branch you mention in such a state that someone else would be able to pick up and finish the work? |
AFAIK it already works. Unfortunately, I'm not really using this project anymore, so there isn't much dogfooding going on. I'll try taking it for a test run to make sure coverage, coveralls and docs all work. If all works properly I'll release a new version with the fixes. |
The build was using the cargo-travis along with kcov to generate coverage data and submit it to coveralls. Unfortunately, this stopped working due to a Rust update (roblabla/cargo-travis#66). Additionally, it was difficult to run this tool locally. This commit uses cargo-tarpaulin to generate the test coverage data and upload it to coveralls. Additionally, developers with Linux can easily generate coverage reports locally with tarpaulin. The CONTRIBUTING file is updated with instructions on how to generate coverage reports. See issue #33.
Thanks for creating this @roblabla! I use it all the time :)
Today, however I have started seeing an error after the compilation of kcov:
See the build log here
Do you know how to solve this?
The text was updated successfully, but these errors were encountered: