-
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
Seeing bad cache invalidation in makerdao/spells-mainnet #316
Comments
thanks for this, |
oh I finally figured out what's causing this, I believe this is simply an oversight in the change detection, |
Tried this again. Still getting the same issue. Oddly enough I'm using test inheritance in another project and that one works fine. Here is steps to reproduce on
You should see a change in the number of failing tests 4 succeeding vs 11. Here is another repo where I've used test inheritance: https://github.com/makerdao/dss-test/blob/master/src/tests/IntegrationTest_0_8_9.t.sol This one seems to work without |
thanks! tried to replicate the case here which seems to work properly, |
Have you tried my exact replication steps outside of that test? There is something in particular about spells-mainnnet that is broken. |
finally found what I believe is the actual root cause for this, it has to do with how we're currently managing the absolute path and the source name of contracts which gets mixed up somehow, probably a remappings/cache/absolute path snafu. this is also the cause for gakonst/ethers-rs#727. I know how to fix that now and also test against it. |
@hexonaut This should no longer be a prooblem since gakonst/ethers-rs#802. Feel free to remove |
Steps to reproduce:
--force
arg fromtest-dssspell-forge.sh
.make test-forge
.src/DssSpell.t.base.sol
line 294 and set thedeployed_spell
toaddress(0)
.make test-forge
.Expected output:
Most tests should start passing (11 succeed, 2 failing) with no mention of spell already cast.
Actual output:
Identical from the first test which is incorrect.
The text was updated successfully, but these errors were encountered: