-
Notifications
You must be signed in to change notification settings - Fork 3
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
Adding infrastructure for multichip tests #231
Conversation
60f1a95
to
d2dcb1e
Compare
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## main #231 +/- ##
==========================================
+ Coverage 77.82% 78.09% +0.27%
==========================================
Files 21 21
Lines 1028 986 -42
==========================================
- Hits 800 770 -30
+ Misses 228 216 -12 ☔ View full report in Codecov by Sentry. |
4c2f7ac
to
0086d31
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.
A lot of comments just organizational and naming-wise. Once that is resolved, I'll take another look.
148c3ae
to
aaf46cf
Compare
ec6db0f
to
1863d25
Compare
c9b3693
to
20542c4
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.
All good, minor comments below.
20542c4
to
4aeb594
Compare
4aeb594
to
3baadca
Compare
Part of issue #211 Integrating new tester class, called `MultichipTester`, into our testing infrastructure in`tt-xla`. It will receive the input and output shardings from the user, the function to be tested, and the golden function which will run on CPU, in a non-sharded mode. It runs the received data and compared the results.
Ticket
Part of issue #211
Problem description
Integrating new tester class, called
MultichipTester
, into our testing infrastructure intt-xla
. It will receive the input and output shardings from the user, the function to be tested, and the golden function which will run on CPU, in a non-sharded mode. It runs the received data and compared the results.