-
Notifications
You must be signed in to change notification settings - Fork 162
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
delete baseBalanceOf #311
delete baseBalanceOf #311
Conversation
d306c0f
to
c3e5b24
Compare
435bcbb
to
94f1fa1
Compare
af59095
to
7be8007
Compare
beb5140
to
4799cab
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.
👍
This PR has a funny element to it; one of the flaky tests from #319 fails every time we run the
The unit tests pass, but this flaky test always fails. I'm fairly certain if I merge #319 and rebase this PR, it should pass the Coverage job. But I'm somewhat weirded out that a test could always pass when run with |
Knowing that coverage tests run slower does it still weird you out? |
4799cab
to
209e42c
Compare
@jflatow nice, that makes sense |
No description provided.