-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Create minifier to identify errors #163
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #163 +/- ##
==========================================
- Coverage 61.08% 59.02% -2.07%
==========================================
Files 22 22
Lines 2850 2987 +137
Branches 610 635 +25
==========================================
+ Hits 1741 1763 +22
- Misses 920 1032 +112
- Partials 189 192 +3 ☔ View full report in Codecov by Sentry. |
Fixes #162 |
def _compare_tensors( | ||
expected: torch.Tensor, | ||
actual: torch.Tensor, | ||
) -> tuple[float, float]: | ||
# Move tensors to the same device | ||
expected = expected.detach().cpu() | ||
actual = actual.detach().cpu() | ||
if expected.dtype == torch.bool: |
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.
Do we need to compare the dtype to make sure they are equal before we compare their values?
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.
In theory no because ort would have complained already. But we could check
Expose the verification module