Improve latency tests #104
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Instead of using the packaged generate_latency_report.py script, use the seapath tool sv_timestamp_analysis. It is a more advanced tool for analysing timestamps between a publisher and a subscriber. Signed-off-by: Elinor Montmasson <[email protected]>
This script won't be used anymore. Tool sv_timestamp_analysis is now used instead. Signed-off-by: Elinor Montmasson <[email protected]>
|
TODO: paths for the generated graphs/.adoc and tweak integration in report if needed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Instead of using the
generate_latency_report.pyscript, usesv_timestamp_analysiswhich is more advanced and can handle for example sv dropsThis draft still need to be fully tested