Skip to content

[BugFix] Fix broken unit tests caused by removal of torch.testng.assert_allclose #644

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

Merged
merged 1 commit into from
Nov 4, 2022

Conversation

sosmond
Copy link
Contributor

@sosmond sosmond commented Nov 3, 2022

Description

Replaced torch.testing.assert_allclose with torch.testing.assert_close

Motivation and Context

close #643

  • I have raised an issue to propose this change (required for new features and bug fixes)

Types of changes

What types of changes does your code introduce? Remove all that do not apply:

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds core functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation (update in the documentation)
  • Example (update in the folder of examples)

Checklist

Go over all the following points, and put an x in all the boxes that apply.
If you are unsure about any of these, don't hesitate to ask. We are here to help!

  • I have read the CONTRIBUTION guide (required)
  • My change requires a change to the documentation.
  • I have updated the tests accordingly (required for a bug fix or a new feature).
  • I have updated the documentation accordingly.

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Nov 3, 2022
@codecov
Copy link

codecov bot commented Nov 3, 2022

Codecov Report

Merging #644 (8daa9f3) into main (e96fd37) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #644   +/-   ##
=======================================
  Coverage   87.82%   87.82%           
=======================================
  Files         125      125           
  Lines       24280    24280           
=======================================
  Hits        21324    21324           
  Misses       2956     2956           
Flag Coverage Δ
habitat-gpu 23.95% <ø> (ø)
linux-cpu 85.11% <100.00%> (ø)
linux-gpu 86.43% <100.00%> (ø)
linux-outdeps-gpu 75.69% <100.00%> (ø)
linux-stable-cpu 85.00% <100.00%> (+0.01%) ⬆️
linux-stable-gpu 86.31% <100.00%> (ø)
macos-cpu 84.89% <100.00%> (+0.01%) ⬆️
olddeps-gpu 76.54% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
test/test_rb.py 97.05% <100.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@sosmond sosmond marked this pull request as ready for review November 3, 2022 22:40
Copy link
Collaborator

@vmoens vmoens left a comment

Choose a reason for hiding this comment

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

LGTM thanks!

@vmoens vmoens merged commit 7faf1e8 into pytorch:main Nov 4, 2022
@sosmond sosmond deleted the fix_unit_tests branch November 4, 2022 04:50
vmoens added a commit that referenced this pull request Nov 4, 2022
* Distributed replay buffer prototype

* Fixes comment issue

* Makes ReplayBufferNode subclass TensorDictReplayBuffer

* aha

* amend

* bf

* Fixes print statements and removes redundant Collector arg

* Fixes print statements and removes redundant Collector arg

* amend

* amend

* Timing larger tensordict transfers over torch rpc using multiple storage types

* init

* amend

* amend

* update_ and make sure content is read

* amend

* amend

* Fixes list storage arg

* Moves benchmark to new top-level directory and adds note in documentation about speed up using MemmapTensor

* Removes analysis.ipynb

* Removes accidental edit to tensordict.py

* Updates data.rst text

* Removes redundant variable

* Removes hack to get list read to work

* replace assert_allclose with assert_close (#644)

* Adds small note illustrating example usage

Co-authored-by: Adi Goel <adityagoel@fb.com>
Co-authored-by: vmoens <vincentmoens@gmail.com>
Co-authored-by: sosmond <35877775+sosmond@users.noreply.github.com>
@vmoens vmoens added the bug Something isn't working label Nov 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants