-
Notifications
You must be signed in to change notification settings - Fork 46
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
sof_perf_analyzer: add skip-to-first-trace option #1100
Conversation
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.
This patch fixes the problem that I had. Thank you very much!
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.
The pylint warning may go away if you drop the too broad except?
In CI test, some traces from previous test case will apprear in the mtrace of current test case, this is a know issue. Previously, we always skip to the first valid trace of this test case, this could raise trouble for developer use of this script. This patch adds skip-to-first-trace option, for CI test, this option should be set (True), and for developer use, this option should be left as it is (False). Signed-off-by: Chao Song <[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.
Nit: could you add a blank line before 190?
Note: still a Github Draft
Due to a known issue in CI test, some traces from previous test case will apprear in the mtrace of current test case. Set skip-to-first-trace option to skip those traces. Signed-off-by: Chao Song <[email protected]>
The skip_to_first_trace() function either return a value or raise an exception. Currently there is no good way to do type annotation for such function, so remove its type annotation. Signed-off-by: Chao Song <[email protected]>
Thanks Marc, the test is good, see internal result 31419, merge |
In CI test, some traces from previous test case will apprear in the mtrace of current test case, this is a know issue.
Previously, we always skip to the first valid trace of this test case, this could raise trouble for developer use of this script.
This patch adds skip-to-first-trace option, for CI test, this option should be set (True), and for developer use, this option should be left as it is (False).