-
Notifications
You must be signed in to change notification settings - Fork 259
fix benchmark build fail and test fail #664 #665
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
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: DogDu <[email protected]>
Welcome @Dog-Du! It looks like this is your first PR to tikv/grpc-rs 🎉 |
Signed-off-by: DogDu <[email protected]>
Signed-off-by: DogDu <[email protected]>
Signed-off-by: DogDu <[email protected]>
Signed-off-by: DogDu <[email protected]>
#[arg(id = "driver_port", long)] | ||
driver_port0: Option<u16>, | ||
/// The port the worker should listen on. For example, 8080 | ||
#[arg(id = "driver-port", long)] | ||
driver_port1: Option<u16>, |
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.
Why add a new port? what's difference between driver_port
and driver-port
?
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.
No difference, only one of them is not None
, just to support both --driver-port
and --driver_port
.
we need --driver_port
when running python3 tools/run_tests/run_performance_tests.py -l rust
close issue: #664
build benchmark fail.
we need to add
derive
feature when importingclap
benchmark test fail.
we need to add the argument
--driver_port