Skip to content
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

The lcov process too slow #1893

Closed
Shylock-Hg opened this issue Mar 9, 2020 · 3 comments · Fixed by #1943
Closed

The lcov process too slow #1893

Shylock-Hg opened this issue Mar 9, 2020 · 3 comments · Fixed by #1943
Assignees

Comments

@Shylock-Hg
Copy link
Contributor

Please check the FAQ documentation before raising an issue

Please check the FAQ documentation and old issues before raising an issue in case someone has asked the same question that you are asking.

Describe the bug (must be provided)

A clear and concise description of what the bug is.

Your Environments (must be provided)

  • OS: uname -a
  • Compliler: g++ --version or clang++ --version
  • CPU: lscpu
  • Commit id (e.g. a3ffc7d8)

How To Reproduce(must be provided)

Steps to reproduce the behavior:

  1. Step 1
  2. Step 2
  3. Step 3

Expected behavior

A clear and concise description of what you expected to happen.

Additional context

Provide logs and configs, or any other context to trace the problem.

@Shylock-Hg
Copy link
Contributor Author

A faster alternatives https://github.com/RPGillespie6/fastcov , but maintained personally.

@Shylock-Hg Shylock-Hg self-assigned this Mar 9, 2020
@Shylock-Hg
Copy link
Contributor Author

Shylock-Hg commented Mar 12, 2020

Or consider llvm-cov.But the llvm-profdata can't process ziped data even if I disable zip when compiling. Built llvm with zlib enabled seems workable but not stable and could only show on testing coverage can't combine to one report.

@Shylock-Hg
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant