8000 [Upstream] [Build] Clean all coverage files during make clean by lyricidal · Pull Request #372 · PRCYCoin/PRCYCoin · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[Upstream] [Build] Clean all coverage files during make clean #372

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

Merged
merged 1 commit into from
Feb 23, 2023

Conversation

lyricidal
Copy link

This adds extra paths that were left out and ensures that .gcda and .gcno files are properly cleaned up.

Simple way to test this is to run the following chain of commands both without and with the changeset:

./configure --enable-lcov
make
make clean && make distclean
find . -name "*.gcno"

Without this, there are leftover (non-cleaned) .gcno files, which could cause errors due to stale or fragmented/incomplete information when attempting to generate the coverage report (make cov). With this change, the find command shows that no such .gcno files remain after cleaning.

This all requires that lcov is available on the system, as configure will properly error out when using the --enable-lcov option if it isn't found.

from PIVX-Project/PIVX#910 with some updates for additional paths that we have from more recent backports.

This adds extra paths that were left out and en
8000
sures that `.gcda` and `
.gcno` files are properly cleaned up.
@lyricidal lyricidal added the Upstream Upstream backports/fixes label Feb 23, 2023
@lyricidal lyricidal merged commit 1f4e22c into develop Feb 23, 2023
@lyricidal lyricidal deleted the upstream-clean_lcov-pr910 branch February 23, 2023 20:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Upstream Upstream backports/fixes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0