You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unclear how to read the coverage report when there is no additional information from Echidna on the state of these properties.
As an example, for the following screenshot, I'm not sure how to interpret this. What happened on the USDC.borrow for it to never be hit, but the DAI borrow could occur?
On the flip side, how should I interpret the following? The fuzzer never showed me an assertion failure on this property, so my intuition is that it should be successful (therefore all statements running green)? - yet the assertWithMsg is showing up as red.
Do you have an screenshot on how this is covered by medusa? If the coverage looks the same, then it looks like an issue with the sourcemap, otherwise, it could be a bug in echidna.
If I'm not mistaken, Medusa was hitting all green on the second example for setCTokenCollateralCaps_should_succeed, but was unable to hit the first example (related to repays / borrows).
Unfortunately don't have a screenshot of it though.. current version of coverage output (i.e: post-rebase) does not hit this function
Describe the issue:
Unclear how to read the coverage report when there is no additional information from Echidna on the state of these properties.
As an example, for the following screenshot, I'm not sure how to interpret this. What happened on the USDC.borrow for it to never be hit, but the DAI borrow could occur?
On the flip side, how should I interpret the following? The fuzzer never showed me an assertion failure on this property, so my intuition is that it should be successful (therefore all statements running green)? - yet the
assertWithMsg
is showing up as red.Code example to reproduce the issue:
Curvance :)
Version:
Echidna 2.2.3
Relevant log output:
No response
The text was updated successfully, but these errors were encountered: