-
Notifications
You must be signed in to change notification settings - Fork 6.2k
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
[telemetry] Move library usage tests out of core #51161
Conversation
…es/mask-data-dir
…es/mask-rllib-dir
@sven1977 @justinvyu @raulchen @matthewdeng please review the relevant files and stamp for codeowner |
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.
train/tune looks good for current state. I can update tests in my PR to reflect desired behavior.
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.
LGTM. All good on RLlib side.
…es/mv-library-usage
Splits the tests for library-specific telemetry data into their own test files. Each one has a similarly-structured test with a shared utility for common logic. This exercise many issues in the telemetry that we need to address in follow ups: - ray-project#51163 - ray-project#51164 - ray-project#51165 - ray-project#51166 - ray-project#51167 - ray-project#51168 --------- Signed-off-by: Edward Oakes <ed.nmi.oakes@gmail.com>
Splits the tests for library-specific telemetry data into their own test files. Each one has a similarly-structured test with a shared utility for common logic. This exercise many issues in the telemetry that we need to address in follow ups: - ray-project#51163 - ray-project#51164 - ray-project#51165 - ray-project#51166 - ray-project#51167 - ray-project#51168 --------- Signed-off-by: Edward Oakes <ed.nmi.oakes@gmail.com>
Splits the tests for library-specific telemetry data into their own test files. Each one has a similarly-structured test with a shared utility for common logic. This exercise many issues in the telemetry that we need to address in follow ups: - ray-project#51163 - ray-project#51164 - ray-project#51165 - ray-project#51166 - ray-project#51167 - ray-project#51168 --------- Signed-off-by: Edward Oakes <ed.nmi.oakes@gmail.com> Signed-off-by: Jay Chia <17691182+jaychia@users.noreply.github.com>
Splits the tests for library-specific telemetry data into their own test files. Each one has a similarly-structured test with a shared utility for common logic. This exercise many issues in the telemetry that we need to address in follow ups: - ray-project#51163 - ray-project#51164 - ray-project#51165 - ray-project#51166 - ray-project#51167 - ray-project#51168 --------- Signed-off-by: Edward Oakes <ed.nmi.oakes@gmail.com> Signed-off-by: Jay Chia <17691182+jaychia@users.noreply.github.com>
Splits the tests for library-specific telemetry data into their own test files. Each one has a similarly-structured test with a shared utility for common logic. This exercise many issues in the telemetry that we need to address in follow ups: - ray-project#51163 - ray-project#51164 - ray-project#51165 - ray-project#51166 - ray-project#51167 - ray-project#51168 --------- Signed-off-by: Edward Oakes <ed.nmi.oakes@gmail.com>
Splits the tests for library-specific telemetry data into their own test files. Each one has a similarly-structured test with a shared utility for common logic. This exercise many issues in the telemetry that we need to address in follow ups: - ray-project#51163 - ray-project#51164 - ray-project#51165 - ray-project#51166 - ray-project#51167 - ray-project#51168 --------- Signed-off-by: Edward Oakes <ed.nmi.oakes@gmail.com> Signed-off-by: Dhakshin Suriakannu <d_suriakannu@apple.com>
Why are these changes needed?
Splits the tests for library-specific telemetry data into their own test files. Each one has a similarly-structured test with a shared utility for common logic.
This exercise many issues in the telemetry that we need to address in follow ups:
ray.init
isn't reported #51164ray.init
is not reported #51167Related issue number
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/
under thecorresponding
.rst
file.