-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Refine trace command descriptions #213
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
Conversation
I would like to ask @lumynou5 for confirmation. |
The change is OK for me, but I prefer minimal changes to the purpose. For example, just append the missing description to the original first line. |
There were several reasons for considering the addition of a dedicated line listing the functions required for each test:
I completely agree that The revised format will likely be: If you have any suggestions, feel free to share them. |
c251922
to
9a279be
Compare
9a279be
to
9a845a2
Compare
9a845a2
to
269877f
Compare
Updated the trace command files to specify required operations explicitly. Improved documentation without modifying test data. Change-Id: If8ef44171bb5cc3cfee812d74cc33d55f6f1320b
269877f
to
28ac74a
Compare
Thank @Dennis40816 for contributing! |
During testing, an error occurred in the process of executing 'trace-03-ops.cmd'. Upon investigation, it was found that the issue was caused by an incorrect implementation of 'q_reverse'. However, this function was not explicitly listed in the trace command descriptions, which could reduce debugging efficiency. Therefore, this PR updates the descriptions in the trace command files.
This PR does not modify any test data.