-
Notifications
You must be signed in to change notification settings - Fork 529
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
Handled the case in which child span starts before and ends after parent span. #1780
Handled the case in which child span starts before and ends after parent span. #1780
Conversation
…t span Signed-off-by: GLVS Kiriti <[email protected]>
Codecov ReportPatch coverage is 📢 Thoughts on this report? Let us know!. |
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.
Please add unit test
…ction Signed-off-by: GLVS Kiriti <[email protected]>
packages/jaeger-ui/src/components/TracePage/CriticalPath/index.test.js
Outdated
Show resolved
Hide resolved
packages/jaeger-ui/src/components/TracePage/CriticalPath/index.test.js
Outdated
Show resolved
Hide resolved
packages/jaeger-ui/src/components/TracePage/CriticalPath/index.test.js
Outdated
Show resolved
Hide resolved
Basically the first test is to test computeCriticalPath function. But memoizedTraceCriticalPath returns the same as computeCriticalPath function. Then should I remove the 2nd test case?? |
Updated sentence in the test case Co-authored-by: Yuri Shkuro <[email protected]> Signed-off-by: GLVSKiriti <[email protected]>
I would remove the first one, it's calling internal implementation details which are irrelevant for the purpose of the test. |
Signed-off-by: GLVSKiriti <[email protected]>
Signed-off-by: GLVSKiriti <[email protected]>
Signed-off-by: GLVSKiriti <[email protected]>
Signed-off-by: GLVSKiriti <[email protected]>
The above case is not handled in previous code
Resolves #1779