-
You must be signed in to change notification settings -
test: added a test for docmatrix in the tail pea #2537
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2537 +/- ##
==========================================
+ Coverage 85.67% 86.29% +0.61%
==========================================
Files 152 152
Lines 9462 9503 +41
==========================================
+ Hits 8107 8201 +94
+ Misses 1355 1302 -53
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
(1, 2) should work now. What I am not sure about with |
1a9f369
to
921306b
Compare
@pytest.mark.timeout(5) | ||
@pytest.mark.parametrize('num_replicas, num_shards', [(1, 1), (2, 2)]) | ||
def test_sharding_tail_pea(num_replicas, num_shards): | ||
"""TODO(Maximilian): Make (1, 2) and (2, 1) also workable""" |
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.
opened an issue for this #2547
* test: added a test for docmatrix in the tail pea * test: added also merge before in follow up pod * test: added multimodal version of uses before * test: fix parametrization and init param * ci: ignore test file in black * test: added black back to tests Co-authored-by: cristian <cristianmtr@users.noreply.github.com> Co-authored-by: cristian mtr <cristian.mitroi@jina.ai>
This is a test showcasing, how a
MatchMerger
in a TailPea could look like. Beware, that replica/sharding for(1,2)
and(2,1)
are broken. That needs to be fixed before 2.0 release.