forked from ray-project/ray
-
Notifications
You must be signed in to change notification settings - Fork 1
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
[pull] master from ray-project:master #2374
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
--------- Signed-off-by: kaihsun <[email protected]>
Signed-off-by: Yi Cheng <[email protected]>
Signed-off-by: woshiyyya <[email protected]>
Signed-off-by: Stefan Schneider <[email protected]>
Signed-off-by: woshiyyya <[email protected]>
Nsight internal docs: https://docs.google.com/document/d/11RlNTbGLf6fat7HYARU8yWhodBD9j5uiZCdAB0geEik Related issue: #39094 Nsight integration with Ray using runtime_env. Currently nsight can't profile the GPU usage from Ray tasks/actors since the processes that can be traced by nsight must be driver processes and it's subprocesses, whereas Ray tasks/actors are run by worker process. Thus, we added nsight native to runtime_env in order to modify the worker process to run with nsys profile which can produce the report for each worker processes once it exits. The nsight API in the runtime_env can be specified with flags that user want to add to the nsys profile for example @ray.remote(runtime_env={"nsight": ["-t", "cuda,nvtx", "--cudabacktrace=True"]}) def task(): ....
Now that we drop Python 3.7 support for Ray 2.8, we can remove the `typing_extensions` dependency.
Signed-off-by: Yunxuan Xiao <[email protected]>
Signed-off-by: woshiyyya <[email protected]>
Migrate ml gpu tests to civ2. Merge train, air and example tests into one job. This reduces 2.5x of total job time. --------- Signed-off-by: can <[email protected]>
The test sometimes got timeout is because the key generation takes a long time. This fix just pre-generate the related files and use that to save time.
This PR makes the RuntimeEnvAgent process bind on 0.0.0.0 when --node-ip-address is set, rather than trying to bind on the node IP address itself. This behaviour is consistent with other processes such as the dashboard agent: ray/dashboard/agent.py Line 116 in 67593a9 grpc_ip = "127.0.0.1" if self.ip == "127.0.0.1" else "0.0.0.0"
No longer supported.
Now that we remove Python 3.7 support, we don't need the pickle5 backport any more :)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )