-
Notifications
You must be signed in to change notification settings - Fork 0
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
cleanup tests & test support code #211
Conversation
593e47f
to
c065238
Compare
I was able to fix the failing test locally by increasing the budget tolerance from I've lost write privileges to these branches. @sentilesdal would you mind pushing up a commit with that fix to see if CI passes after? |
33c1a9b
to
201b048
Compare
505b38c
to
693241e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Went through with Dylan IRL. This is basically just test cleanups right before he left. Approved.
Lingering issues are summarized here #136 (comment) |
Description
calculate_open_short
tosolvency_after_short
. And we now callsolvency_after_short
incalculate_open_short
. This diverges a bit from Solidity because we do not split theapply_open_short
function from thecalculate_open_short
function in rust. This means it was possible to get a valid answer fromcalculate_open_short
that would revert in the contract. That should be fixed, now.solvency_after_short(min_txn)
instead of the incorrect check it was doing.get_max_short
function from the preamble. We don't need all of the extra checks.agent.calculate_max_short
calculate_short_bonds_given_deposit
tomaybe_base_tolerance=1e10
(from1e9
) andmaybe_max_iterations=1_000
(from500
).