[rllib] Decreases log quantity for learning tests#59005
Conversation
Signed-off-by: Mark Towers <mark@anyscale.com>
|
Reviewing the buildkite logs, the problem isn't the Tune CLIReporter frequency as I originally believed but the print of the results after each train I believe. |
|
This pull request has been automatically marked as stale because it has not had You can always ask for help on our discussion forum or Ray's public slack channel. If you'd like to keep this open, just leave any comment, and the stale label will be removed. |
|
This pull request has been automatically closed because there has been no more activity in the 14 days Please feel free to reopen or open a new pull request if you'd still like this to be addressed. Again, you can always ask for help on our discussion forum or Ray's public slack channel. Thanks again for your contribution! |
# Conflicts: # rllib/utils/test_utils.py
Signed-off-by: Mark Towers <mark@anyscale.com>
Signed-off-by: Mark Towers <mark@anyscale.com>
rllib/BUILD.bazel
Outdated
| ], | ||
| # Include the offline data files. | ||
| data = [ | ||
| "--tune-max-report-freq=30", |
There was a problem hiding this comment.
Argument incorrectly placed in Bazel data instead of args
High Severity
The --tune-max-report-freq=30 argument is added to the data attribute instead of the args attribute in multiple py_test rules. In Bazel, data specifies data files needed at runtime while args specifies command-line arguments. This affects 10 test definitions: learning_tests_cartpole_bc, learning_tests_cartpole_bc_gpu, learning_tests_cartpole_bc_with_offline_evaluation, learning_tests_cartpole_bc_with_offline_evaluation_gpu, learning_tests_pendulum_cql, learning_tests_pendulum_cql_gpu, learning_tests_pendulum_iql, learning_tests_pendulum_iql_gpu, learning_tests_cartpole_marwil, and learning_tests_cartpole_marwil_gpu. The argument won't be passed to the scripts and Bazel may fail trying to find a file with that name.
Additional Locations (2)
Signed-off-by: Mark Towers <mark@anyscale.com>
rllib/examples/utils.py
Outdated
There was a problem hiding this comment.
nit: we can create CLIReporter regardless the value of the args.num_agents (L658).
kamil-kaczmarek
left a comment
There was a problem hiding this comment.
LGTM! Just left smal nit to improve
Signed-off-by: Mark Towers <mark@anyscale.com>
Signed-off-by: Mark Towers <mark@anyscale.com>
## Description Reviewing our testing logs, they can often be incredibly long. This PR aims to reduce them by changing three things 1. By default, the CLIReporter in `run_rllib_example_script_experiment` will report an algorithms training results at least every 5 seconds. This PR adds a `tune-max-report-freq` argument that we keep at 5 for end-users while in tests we change it to 30 seconds 2. Change the verbosity of the tune results from 2 to 1 when testing 3. Removed ` WARNING impala_learner.py:576 -- No old learner state to remove from the queue.` warnings --------- Signed-off-by: Mark Towers <mark@anyscale.com> Co-authored-by: Mark Towers <mark@anyscale.com> Signed-off-by: jasonwrwang <jasonwrwang@tencent.com>
## Description Reviewing our testing logs, they can often be incredibly long. This PR aims to reduce them by changing three things 1. By default, the CLIReporter in `run_rllib_example_script_experiment` will report an algorithms training results at least every 5 seconds. This PR adds a `tune-max-report-freq` argument that we keep at 5 for end-users while in tests we change it to 30 seconds 2. Change the verbosity of the tune results from 2 to 1 when testing 3. Removed ` WARNING impala_learner.py:576 -- No old learner state to remove from the queue.` warnings --------- Signed-off-by: Mark Towers <mark@anyscale.com> Co-authored-by: Mark Towers <mark@anyscale.com>
## Description Reviewing our testing logs, they can often be incredibly long. This PR aims to reduce them by changing three things 1. By default, the CLIReporter in `run_rllib_example_script_experiment` will report an algorithms training results at least every 5 seconds. This PR adds a `tune-max-report-freq` argument that we keep at 5 for end-users while in tests we change it to 30 seconds 2. Change the verbosity of the tune results from 2 to 1 when testing 3. Removed ` WARNING impala_learner.py:576 -- No old learner state to remove from the queue.` warnings --------- Signed-off-by: Mark Towers <mark@anyscale.com> Co-authored-by: Mark Towers <mark@anyscale.com>
## Description Reviewing our testing logs, they can often be incredibly long. This PR aims to reduce them by changing three things 1. By default, the CLIReporter in `run_rllib_example_script_experiment` will report an algorithms training results at least every 5 seconds. This PR adds a `tune-max-report-freq` argument that we keep at 5 for end-users while in tests we change it to 30 seconds 2. Change the verbosity of the tune results from 2 to 1 when testing 3. Removed ` WARNING impala_learner.py:576 -- No old learner state to remove from the queue.` warnings --------- Signed-off-by: Mark Towers <mark@anyscale.com> Co-authored-by: Mark Towers <mark@anyscale.com> Signed-off-by: peterxcli <peterxcli@gmail.com>
## Description Reviewing our testing logs, they can often be incredibly long. This PR aims to reduce them by changing three things 1. By default, the CLIReporter in `run_rllib_example_script_experiment` will report an algorithms training results at least every 5 seconds. This PR adds a `tune-max-report-freq` argument that we keep at 5 for end-users while in tests we change it to 30 seconds 2. Change the verbosity of the tune results from 2 to 1 when testing 3. Removed ` WARNING impala_learner.py:576 -- No old learner state to remove from the queue.` warnings --------- Signed-off-by: Mark Towers <mark@anyscale.com> Co-authored-by: Mark Towers <mark@anyscale.com> Signed-off-by: peterxcli <peterxcli@gmail.com>
Description
Reviewing our testing logs, they can often be incredibly long. This PR aims to reduce them by changing three things
run_rllib_example_script_experimentwill report an algorithms training results at least every 5 seconds. This PR adds atune-max-report-freqargument that we keep at 5 for end-users while in tests we change it to 30 secondsWARNING impala_learner.py:576 -- No old learner state to remove from the queue.warnings