Skip to content

[Docs][KubeRay] Fix RayJob quickstart doc step 9 error #53887

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

Conversation

MortalHappiness
Copy link
Member

@MortalHappiness MortalHappiness commented Jun 17, 2025

Why are these changes needed?

Step 9 should show no RayClusters. It shows one cluster because it is still being deleted, but we didn't wait for it.

This PR added one ignored cell, polling wait for the RayCluster being deleted.

I've already rerun the whole jupyter notebook.

Related issue number

Checks

  • 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 :(

@MortalHappiness MortalHappiness marked this pull request as ready for review June 17, 2025 15:14
@Copilot Copilot AI review requested due to automatic review settings June 17, 2025 15:14
@MortalHappiness MortalHappiness requested review from pcmoritz, kevin85421 and a team as code owners June 17, 2025 15:14
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR fixes an error in the RayJob quickstart documentation by updating step 9 to ignore output from deleted clusters.

  • Updated notebook cell metadata to include "remove-output" and "nbval-ignore-output" tags
  • Ensures the expected output (i.e., no RayClusters displayed) without affecting test coverage

@MortalHappiness MortalHappiness marked this pull request as draft June 17, 2025 15:17
Signed-off-by: Chi-Sheng Liu <chishengliu@chishengliu.com>
@MortalHappiness MortalHappiness force-pushed the docs/kuberay-rayjob-quickstart-step-9-error branch from 11b8a48 to af4475a Compare June 17, 2025 15:34
@MortalHappiness MortalHappiness added the go add ONLY when ready to merge, run all tests label Jun 17, 2025
@MortalHappiness MortalHappiness marked this pull request as ready for review June 17, 2025 15:34
"rayjob-sample-raycluster-7965c-small-group-worker-nlzwx 1/1 Running 0 117s\n",
"rayjob-sample-74pmj 1/1 Running 0 2s\n"
"kuberay-operator-6bc45dd644-lc45k 1/1 Running 0 81s\n",
"rayjob-sample-raycluster-jbd9q-head-66cgd 1/1 Running 0 58s\n",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you use v1.4? In my memory, the head should not have suffix 66cgd if you use v1.4.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is another PR to update the KubeRay version for doctests and then rerun them all. But it needs to wait for the formal release to use 1.4.0 version.

#53883

@kevin85421
Copy link
Member

cc @jjyao @edoakes would you mind merging this PR? Thanks!

@jjyao jjyao merged commit 34b067b into ray-project:master Jun 18, 2025
6 checks passed
minerharry pushed a commit to minerharry/ray that referenced this pull request Jun 27, 2025
…3887)

Signed-off-by: Chi-Sheng Liu <chishengliu@chishengliu.com>
elliot-barn pushed a commit that referenced this pull request Jul 2, 2025
Signed-off-by: Chi-Sheng Liu <chishengliu@chishengliu.com>
Signed-off-by: elliot-barn <elliot.barnwell@anyscale.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
go add ONLY when ready to merge, run all tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants