[core] Remove unused core_worker_test

.buildkite/pipeline.macos.yml

@@ -68,7 +68,7 @@ steps:
     # Use --dynamic_mode=off until MacOS CI runs on Big Sur or newer. Otherwise there are problems with running tests
     # with dynamic linking.
     - bazel test --config=ci --dynamic_mode=off --test_env=CI $(./ci/run/bazel_export_options) --build_tests_only --test_tag_filters=-post_wheel_build --
-      //:all python/ray/serve/... python/ray/dashboard/... -rllib/... -core_worker_test
+      //:all python/ray/serve/... python/ray/dashboard/... -rllib/...
     # clang-format is needed by java/test.sh
     - pip install clang-format==12.0.1
     - ./java/test.sh

.buildkite/pipeline.yml

@@ -167,7 +167,7 @@
     - cleanup() { if [ "${BUILDKITE_PULL_REQUEST}" = "false" ]; then ./ci/build/upload_build_info.sh; fi }; trap cleanup EXIT
     - bazel test --config=ci --config=llvm $(./ci/run/bazel_export_options)
       --build_tests_only
-      -- //:all -rllib/... -core_worker_test
+      -- //:all -rllib/...
 
 - label: ":cpp: Tests (ASAN)"
   conditions: [ "RAY_CI_CORE_CPP_AFFECTED" ]
@@ -176,7 +176,7 @@
     - bazel test --config=ci --config=asan-clang $(./ci/run/bazel_export_options)
       --build_tests_only
       --jobs=2
-      -- //:all -//:core_worker_test
+      -- //:all
 
 - label: ":cpp: Tests (UBSAN)"
   conditions: [ "RAY_CI_CORE_CPP_AFFECTED" ]
@@ -185,7 +185,7 @@
     - bazel test --config=ci --config=ubsan $(./ci/run/bazel_export_options)
       --build_tests_only
       --jobs=2
-      -- //:all -//:core_worker_test -//:logging_test
+      -- //:all -//:logging_test
 
 - label: ":cpp: Tests (TSAN)"
   conditions: [ "RAY_CI_CORE_CPP_AFFECTED" ]
@@ -194,7 +194,7 @@
     - bazel test --config=ci --config=tsan-clang $(./ci/run/bazel_export_options)
       --build_tests_only
       --jobs=2
-      -- //:all -//:core_worker_test -//:event_test -//:gcs_actor_manager_test
+      -- //:all -//:event_test -//:gcs_actor_manager_test
       -//:gcs_placement_group_manager_test -//:gcs_placement_group_scheduler_test
       -//:gcs_server_rpc_test -//:gcs_client_test
       -//:metric_exporter_client_test -//:stats_test -//:worker_pool_test

BUILD.bazel

@@ -839,36 +839,6 @@ cc_binary(
     ],
 )
 
-cc_test(
-    name = "core_worker_test",
-    size = "small",
-    srcs = ["src/ray/core_worker/test/core_worker_test.cc"],
-    args = [
-        "$(location raylet)",
-        "$(location mock_worker)",
-        "$(location gcs_server)",
-        "$(location redis-cli)",
-        "$(location redis-server)",
-    ],
-    copts = COPTS,
-    data = [
-        "//:gcs_server",
-        "//:mock_worker",
-        "//:raylet",
-        "//:redis-cli",
-        "//:redis-server",
-    ],
-    tags = ["team:core"],
-    deps = [
-        ":core_worker_lib",
-        ":gcs",
-        "//src/ray/protobuf:runtime_env_common_cc_proto",
-        "@com_google_absl//absl/container:flat_hash_map",
-        "@com_google_absl//absl/container:flat_hash_set",
-        "@com_google_googletest//:gtest",
-    ],
-)
-
 cc_test(
     name = "memory_store_test",
     size = "small",

ci/ci.sh

@@ -120,7 +120,6 @@ test_core() {
   case "${OSTYPE}" in
     msys)
       args+=(
-        -//:core_worker_test
         -//:event_test
         -//:gcs_pub_sub_test
         -//:gcs_server_test

doc/source/ray-contribute/getting-involved.rst

@@ -222,13 +222,13 @@ The `CI`_ test folder contains all integration test scripts and they
 invoke other test scripts via ``pytest``, ``bazel``-based test or other bash
 scripts. Some of the examples include:
 
-* Raylet integration tests commands:
-    * ``bazel test //:core_worker_test``
+* Ray core C++ unit test commands:
+    * ``bazel test //:reference_count_test``
 
 * Bazel test command:
     * ``bazel test --build_tests_only //:all``
 
-* Ray serving test commands:
+* Ray Serve test commands:
     * ``pytest python/ray/serve/tests``
     * ``python python/ray/serve/examples/echo_full.py``