-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Forge Coverage Always at 0% #3072
Labels
Comments
same issue here! |
Should be fixed in latest master per #3073. |
Repository owner
moved this from Todo
to Done
in Foundry
Sep 4, 2022
trajan0x
added a commit
to synapsecns/sanguine
that referenced
this issue
Sep 5, 2022
This reverts commit a6b87ca.
trajan0x
added a commit
to synapsecns/sanguine
that referenced
this issue
Sep 5, 2022
Foundry nightly release should work now making a6b87ca and #161 no longer neccesary (workarounds for foundry-rs/foundry#3072 and foundry-rs/foundry#3067 respectively Co-authored-by: Trajan0x <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Component
Forge
Have you ensured that all of these are up to date?
What version of Foundry are you on?
1c41585
What command(s) is the bug in?
forge coverage -vvv
Operating System
macOS (Apple Silicon)
Describe the bug
This appears to be a regression in #3068. The memory growth issue (#3067) is fixed, but now coverage is coming across at 0% across repositories.
Steps to replicate:
foundryup -C 1c415857dd7b617190834dbcb361506f6143fed4
git clone https://github.com/transmissions11/solmate
forge coverage -vvv
Output:
Prior to 1c41585 this is coming in at ~59.02% total
The text was updated successfully, but these errors were encountered: