-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[BUG] Code coverage #4142
Comments
Hey @0xAurelou, a friendly suggestion - your issue would be more readable if you put the code in a collapsible Markdown section. |
Hello @PaulRBerg, |
@PaulRBerg No Update or ETA on this issue ? |
@0xAurelou I am not an active Foundry maintainer. |
Sorry my Bad I thought you were. |
@onbjerg Seems like a few code coverage bugs are related to more than one contract having a similar interface. I think code coverage gets attributed to the wrong function/contract if they share bytecode or naming? Not sure what it is, but I've seen several issues with very similar symptoms. Any insight? Thank you |
Component
Forge
Have you ensured that all of these are up to date?
What version of Foundry are you on?
forge 0.2.0 (d8f2434 2023-01-20T00:09:17.907613959Z)
What command(s) is the bug in?
forge coverage
Operating System
Linux
Describe the bug
When I am doing some code coverage the same code can get me a 0% code coverage while it should be 100% (Both compile)
Source Code
mock/USDC.sol
mock/USDT.sol
test/USDC.t.sol
Output
The text was updated successfully, but these errors were encountered: