Skip to content
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

Sharding: Add some tests for sharding codepaths #615

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

hsanjuan
Copy link
Collaborator

@hsanjuan hsanjuan commented Dec 7, 2018

I had these changes laying around on a different branch (along some other code not included here). They are the ones that surfaced the problems with the batching DAGService. Since that was fixed, we can merge these so they are not lost (I think).

License: MIT
Signed-off-by: Hector Sanjuan <code@hector.link>
@hsanjuan hsanjuan self-assigned this Dec 7, 2018
@ghost ghost added the status/in-progress In progress label Dec 7, 2018
@hsanjuan
Copy link
Collaborator Author

hsanjuan commented Dec 7, 2018

Actually one of the tests should fail because it tests the correct unpinning of shared shards. But let's leave this here so I don't forget I need to fix it.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.1%) to 64.789% when pulling 4946aed on tests/shards into 77148e5 on master.

// the files resulting from GetShardingDir*
// They have been obtained by adding the "shardTesting" folder
// the files resulting from shardingTestDir/shadringTestTree folder.
// They have been obtained by adding the that folder
Copy link
Contributor

Choose a reason for hiding this comment

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

the that folder

???

pinDelay()
})

t.Run("shard", func(t *testing.T) {
Copy link
Contributor

Choose a reason for hiding this comment

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

It would be great if each of these tests could have a bit more explanation as to what they are testing as the testcase is hard to grok from the code.

@RubenKelevra
Copy link
Collaborator

RubenKelevra commented May 7, 2022

@hsanjuan mind cleaning this up? Was reading it and then noticed that date :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants