-
Notifications
You must be signed in to change notification settings - Fork 24
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
Implement zmb get_test_params #768
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.
It looks fine. It works as expected. I think we should include all API methods into zmb
(but not in this PR).
@PNAX, can you review this? |
zmb [GLOBAL OPTIONS] get_test_params [OPTIONS] | ||
|
||
Options: | ||
--test-id TEST_ID |
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.
It looks like other methods use --testid
(see test_progress
and get_test_results
). Could you change this one to be consistent with the other ? (Or the other way around).
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.
Outside this change I find two --testid
and one --test-id
. I agree that making them consistent would be good. I might also affect zmtest
for which zmb
is a backend.
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 agree that this sucks, but I actually made it so in order to be consistent with the RPCAPI.
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 think we can start by making it consistent in zmb because it is more likely that you do things manually there. Or support both.
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.
Could you then update all the other one to --test-id
in this PR, so they all evolve together ?
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 just checked and it's inconsistent all over the place. Maybe we should start migrating to testid
for test ids across the board. I'll deprecate all test-id
, test_id
and id
that I can find.
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'll make another update that does away with the deprecations in zmb. It clearly states that it's interface is unstable so we may well make use of that. |
@PNAX, are your comments on this PR adressed by the last updates? |
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.
yes, this looks good to me.
v2021.2 testingLGTM |
Purpose
Add another RPC API method to zmb.
Context
N/A
Changes
Add
zmb get_test_params
.Rename the
--testid
parameter to--test-id
for thetest_progress
andget_test_results
commands. The old parameter name still works but emits a deprecation warning.How to test this PR
Start a test and verify that the output from
get_test_params
looks reasonable:Verify that zmtest still works: