-
Notifications
You must be signed in to change notification settings - Fork 98
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
Make latency_calculator_decorator be usable in longevity tests #9627
Comments
soyacz
added a commit
to soyacz/scylla-cluster-tests
that referenced
this issue
Dec 30, 2024
`latency_calculator_decorator` requires workload to be set. Up to now it was taken from the test name. This change allows to set it by `workload_name` test parameter, so it can be used in all kind of tests. Added latency verification for all 'individual nemesis' cases (proposal, anyway need to test with something). closes: scylladb#9627
3 tasks
soyacz
added a commit
to soyacz/scylla-cluster-tests
that referenced
this issue
Dec 31, 2024
`latency_calculator_decorator` requires workload to be set. Up to now it was taken from the test name. This change allows to set it by `workload_name` test parameter, so it can be used in all kind of tests. Added latency verification for all 'individual nemesis' cases (proposal, anyway need to test with something). closes: scylladb#9627
fruch
pushed a commit
that referenced
this issue
Dec 31, 2024
`latency_calculator_decorator` requires workload to be set. Up to now it was taken from the test name. This change allows to set it by `workload_name` test parameter, so it can be used in all kind of tests. Added latency verification for all 'individual nemesis' cases (proposal, anyway need to test with something). closes: #9627
soyacz
added
backport/none
Backport is not required
and removed
backport/none
Backport is not required
labels
Dec 31, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
latency_calculator_decorator
requires to be run from test with specific name that includes workload type (write, read, mixed). This way it is not usable within typical longevity tests (or manager tests) that have different test names.Make this decorator be usable in any scope.
Idea is to add config param that will specify workload type explicitly rather than taking it from the test name.
The text was updated successfully, but these errors were encountered: