-
Notifications
You must be signed in to change notification settings - Fork 33
[Tests] Mock Observers, Static Lifecycle Tests #482
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
base: main
Are you sure you want to change the base?
Conversation
97a4d16
to
0fdfbd1
Compare
Signed-off-by: Kyle Sayers <[email protected]>
Signed-off-by: Kyle Sayers <[email protected]>
Signed-off-by: Kyle Sayers <[email protected]>
Signed-off-by: Kyle Sayers <[email protected]>
Signed-off-by: Kyle Sayers <[email protected]>
Signed-off-by: Kyle Sayers <[email protected]>
Signed-off-by: Kyle Sayers <[email protected]>
0fdfbd1
to
8973328
Compare
Signed-off-by: Kyle Sayers <[email protected]>
} | ||
|
||
|
||
class ObserverBase(torch.nn.Module): |
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.
Why do we need mock ObserverBase
and MockMovingMinMaxObserver
? If the test asserts they arrive at an expected value, shouldn't we just be using and testing the real things?
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.
Good point, I’ll remove the extra classes
Purpose