We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Forge
forge 0.2.0 (ac81a53 2024-12-02T00:48:39.714560304Z)
forge coverage
Linux
After commit #9438, lcov 1.x sees double the number of total function, so function coverage is always less than 50%.
lcov
Repo that reproduces the issue: https://github.com/KholdStare/foundry-lcov-bug
CI run in that repo that fails, and shows 4 functions from lcov summary when there are only 2: https://github.com/KholdStare/foundry-lcov-bug/actions/runs/12128532756/job/33815097436
The reproduction is based off of running foundry init and running coverage. See the script: https://github.com/KholdStare/foundry-lcov-bug/blob/main/run_coverage.sh
foundry init
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Component
Forge
Have you ensured that all of these are up to date?
What version of Foundry are you on?
forge 0.2.0 (ac81a53 2024-12-02T00:48:39.714560304Z)
What command(s) is the bug in?
forge coverage
Operating System
Linux
Describe the bug
After commit #9438,
lcov
1.x sees double the number of total function, so function coverage is always less than 50%.Repo that reproduces the issue: https://github.com/KholdStare/foundry-lcov-bug
CI run in that repo that fails, and shows 4 functions from
lcov
summary when there are only 2: https://github.com/KholdStare/foundry-lcov-bug/actions/runs/12128532756/job/33815097436The reproduction is based off of running
foundry init
and running coverage. See the script: https://github.com/KholdStare/foundry-lcov-bug/blob/main/run_coverage.shThe text was updated successfully, but these errors were encountered: