mirror of
https://github.com/vale981/ray
synced 2025-03-12 14:16:39 -04:00
6d2806f951
The current inheritance behavior for runtime_envs enables the following workflow for Jobs: A working_dir can be set in the Jobs API, and then inside the driver script, if a new per-task runtime_env is defined, it will automatically inherit the driver's working_dir. There is an ongoing discussion about the best approach for runtime_env inheritance going forward: https://github.com/ray-project/ray/issues/25484, in which we noted that there were no tests covering this behavior. This PR adds integration tests for the above behavior. If we ultimately decide to abandon the current inheritance behavior and instead have child runtime envs completely overwrite the parent runtime env, this test will fail, reminding us to do the following: - Update the internal runtime_env usage in Ray Tune to use the `ray.get_runtime_context().runtime_env.update` API - Update the documentation for Ray Jobs telling users to use `ray.get_runtime_context().runtime_env.update` and update this test |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| check_cuda_devices.py | ||
| consume_one_cpu.py | ||
| override_env_var.py | ||
| per_task_runtime_env.py | ||
| print_namespace.py | ||
| print_runtime_env.py | ||
| ray_tune_basic.py | ||
| ray_tune_dependency.py | ||
| script_with_exception.py | ||