-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Add integration test for ErrTraceNotFound #2478
Add integration test for ErrTraceNotFound #2478
Conversation
Signed-off-by: Yuri Shkuro <[email protected]>
Signed-off-by: Yuri Shkuro <[email protected]>
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.
LGTM - although the title is a bit misleading, as the integration test was already testing for ErrTraceNotFound
, so assume it wasn't being run against badger? But need to fix TestFindNothing
before merging.
This is related to #2471, isn't it? |
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.
I'm blocking this for now, because of the test failure. Looks like the same is being addressed in another PR already, so, we might want to close this.
Signed-off-by: Yuri Shkuro <[email protected]>
@objectiser where do you see integration test checking for NotFound? Badger implementation clearly did not satisfy the API contract for that (which I also fix in this PR), yet it was passing integration tests, so I assume there was no explicit test for NotFound. @jpkrohling I don't know if #2471 is fixing the same issue (and it's doing it incorrectly anyway, findTraces can return empty list). |
Signed-off-by: Yuri Shkuro <[email protected]>
@yurishkuro yep, lgtm. |
I added documentation to the span Reader API with expectations about not-found. |
Codecov Report
@@ Coverage Diff @@
## master #2478 +/- ##
==========================================
+ Coverage 95.52% 95.53% +0.01%
==========================================
Files 208 208
Lines 10750 10756 +6
==========================================
+ Hits 10269 10276 +7
Misses 405 405
+ Partials 76 75 -1
Continue to review full report at Codecov.
|
Thanks for documenting the interface! |
Signed-off-by: Yuri Shkuro <[email protected]>
This is especially interesting when using go-plugin based storage, where the error has to be correctly passed through gRPC client.
The test revealed that Badger did not return NotFound when expected, so it's fixed here as well.
I added documentation to the span Reader API with expectations about not-found.