| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[release] veresion change to 2.48.0 (#54557) Signed-off-by: Lonnie Liu <lonnie@anyscale.com> | 1 年前 | |
[release] veresion change to 2.48.0 (#54557) Signed-off-by: Lonnie Liu <lonnie@anyscale.com> | 1 年前 | |
[release] veresion change to 2.48.0 (#54557) Signed-off-by: Lonnie Liu <lonnie@anyscale.com> | 1 年前 | |
[release] veresion change to 2.48.0 (#54557) Signed-off-by: Lonnie Liu <lonnie@anyscale.com> | 1 年前 | |
[release] veresion change to 2.48.0 (#54557) Signed-off-by: Lonnie Liu <lonnie@anyscale.com> | 1 年前 | |
[core] Place core_worker bazel targets into separate directories (#52032) Signed-off-by: Ziy1-Tan <ajb459684460@gmail.com> | 1 年前 | |
[core] Add readme for java tests (#49320) Signed-off-by: dentiny <dentinyhao@gmail.com> | 1 年前 | |
[docs] Update for typo (#51813) <!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. --> <!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? <!-- Please give a short summary of the change and the problem this solves. --> ## Related issue number <!-- For example: "Closes #1234" --> ## Checks - [x] I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR. - [ ] I've run scripts/format.sh to lint the changes in this PR. - [ ] I've included any doc changes needed for https://docs.ray.io/en/master/. - [ ] I've added any new APIs to the API Reference. For example, if I added a method in Tune, I've added it in doc/source/tune/api/ under the corresponding .rst file. - [ ] I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/ - Testing Strategy - [ ] Unit tests - [ ] Release tests - [ ] This PR is not tested :( Signed-off-by: zhiqiwangebay <147236090+zhiqiwangebay@users.noreply.github.com> | 1 年前 | |
[Java] Format ray java code (#13056) | 5 年前 | |
[Java] Support parallel actor in experimental. (#21701) For the purpose to provide an alternative option for running multiple actor instances in a Java worker process, and the eventual goal is to remove the original multi-worker-instances in one worker process implementation. we're proposing supporting parallel actor concept in Java. This feature enables that users could define some homogeneous parallel execution instances in an actor, and all instances hold one thread as the execution backend. ### Introduction For the following example, we define a parallel actor with 10 parallelism. The backend actor has 10 concurrency groups for the parallel executions, it also means there're 10 threads for that. We can access the instance by the instance handle, like: java ParallelActorHandle<A> actor = ParallelActor.actor(A::new).setParallelism(10).remote(); ParallelInstance<A> instance = actor.getInstance(/*index=*/ 2); Preconditions.checkNotNull(instance); Ray.get(instance.task(A::incr, 1000000).remote()); // print 1000000 instance = actor.getInstance(/*index=*/ 2); Preconditions.checkNotNull(instance); Ray.get(instance.task(A::incr, 2000000).remote().get()); // print 3000000 instance = actor.getInstance(/*index=*/ 3); Preconditions.checkNotNull(instance); Ray.get(instance.task(A::incr, 2000000).remote().get()); // print 2000000 ### Limitation - It doesn't support concurrency group on a parallel actor yet. Co-authored-by: Kai Yang <kfstorm@outlook.com> | 4 年前 | |
Shellcheck comments (#9595) | 5 年前 | |
[Java] Upgrade Commons-io to 2.14 (#44437) <!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. --> <!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? [Java] Upgrade Commons-io to 2.14 commons-io can be upgraded to 2.14.0. commons-io 2.7 is an older version. commons-io 2.14.0 has been verified for a long time and has no direct or indirect CVE issues. ## Related issue number <!-- For example: "Closes #1234" --> ## Checks - [x] I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR. - [ ] I've run scripts/format.sh to lint the changes in this PR. - [ ] I've included any doc changes needed for https://docs.ray.io/en/master/. - [ ] I've added any new APIs to the API Reference. For example, if I added a method in Tune, I've added it in doc/source/tune/api/ under the corresponding .rst file. - [ ] I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/ - Testing Strategy - [ ] Unit tests - [ ] Release tests - [ ] This PR is not tested :( Signed-off-by: Shilun Fan <slfan1989@apache.org> Co-authored-by: Thomas Desrosiers <681004+thomasdesr@users.noreply.github.com> | 1 年前 | |
[CI] Enable end-of-file-fixer (#50050) Enable end-of-file-fixer pre-commit hook to makes sure files end in a newline and only a newline. --------- Signed-off-by: fscnick <fscnick.dev@gmail.com> | 1 年前 | |
[CI] Remove tailing white space [1/N] (#50250) This is part of enabling pre-commit hook trailing-whitespace in lint Signed-off-by: fscnick <fscnick.dev@gmail.com> | 1 年前 | |
[release] veresion change to 2.48.0 (#54557) Signed-off-by: Lonnie Liu <lonnie@anyscale.com> | 1 年前 | |
[Java] Shade jackson to avoid conflict. (#24535) Jackson is a widely-used utility. User from Ant reports the jackson class is conflicted between Ray jar and user's jar. This PR shade the jackson in Ray jar to avoid the conflict. Co-authored-by: Kai Yang <kfstorm@outlook.com> | 4 年前 | |
[ci] set java home on mac ci tests (#53225) required on new mac machines also enables picking en6 for ip address, which is the private network. Signed-off-by: Lonnie Liu <lonnie@anyscale.com> | 1 年前 | |
[Serve] Define Java Backend (#16169) | 4 年前 | |
[Java] Add entry to run custom test using bazel (#26073) Now we can run custom java tests by: 0. cp testng_custom_template.xml testng_custom.xml 1. Specify test class/method in testng_custom.xml 2. bazel test //java:custom_test --test_output=streamed | 4 年前 |
Instructions on ray-java test
- Install necessary executables
javaandjavacis needed to run ray-java tests, and users need to make sure they're accessible in$PATH- You could check whether they're installed by
which javaandwhich javac - Install
javawithsudo apt install openjdk-11-jre -y - Install
javacwithsudo apt install openjdk-11-jdk -y - java-11 is the version we use on CI
- Run java test with bazel
# To run ray tests.
bazel test //java:all_tests --test_output=streamed
# To run custom tests.
bazel test //java:custom_test --test_output=streamed