Skip to content

Conversation

mruberry
Copy link
Collaborator

This test function is confusing since our assertEqual behavior allows for tolerance to be specified, and this is a redundant mechanism.

@mruberry mruberry requested a review from ngimel July 16, 2020 01:13
@dr-ci
Copy link

dr-ci bot commented Jul 16, 2020

💊 CI failures summary and remediations

As of commit fe8c932 (more details on the Dr. CI page):


💚 💚 Looks good so far! There are no failures yet. 💚 💚


This comment was automatically generated by Dr. CI (expand for details).Follow this link to opt-out of these comments for your Pull Requests.

Please report bugs/suggestions on the GitHub issue tracker or post in the (internal) Dr. CI Users group.

See how this bot performed.

This comment has been revised 8 times.

Copy link
Contributor

@facebook-github-bot facebook-github-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mruberry has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

@facebook-github-bot
Copy link
Contributor

@mruberry merged this pull request in b2b8af9.

@mruberry mruberry deleted the remove_assert_almost_equal branch August 21, 2020 19:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants