Skip to content

Conversation

@jovany-wang
Copy link
Collaborator

@jovany-wang jovany-wang commented Aug 6, 2018

What do these changes do?

  1. Enabled cluster test in CI.
  2. Made raylet port configurable in java.

Related issue number

N/A

@jovany-wang jovany-wang requested a review from zhijunfu August 6, 2018 12:09
pkill -9 redis
pkill -9 raylet
ps aux | grep ray | awk '{system("kill "$2);}'
rm /tmp/raylet*
Copy link

Choose a reason for hiding this comment

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

why remove this?

if [ "$1" == "raylet" ]; then
sed -i 's/^use_raylet.*$/use_raylet = true/g' ray.config.ini
else
sed -i 's/^use_raylet.*$/use_raylet = false/g' ray.config.ini
Copy link

Choose a reason for hiding this comment

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

I'm not sure if it's a real problem. But I'd prefer not editing the file in place, because it makes the git state dirty.

Copy link
Collaborator Author

@jovany-wang jovany-wang Aug 6, 2018

Choose a reason for hiding this comment

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

If this way is not great, I will try distinguishing raylet or non raylet mode byOVERWRITE.

Copy link

Choose a reason for hiding this comment

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

using overwrite is fine, or you can create a temp config file

fi

sh cleanup.sh
rm -rf local_deploy
Copy link

Choose a reason for hiding this comment

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

what will be stored in local_deploy? maybe move it to /tmp/local_deploy?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Does CURR_WORK_DIR be not suitable?
@zhijunfu What do you think?

@raulchen
Copy link

raulchen commented Aug 6, 2018

  1. I think it's better to run unit/integration tests in CI, instead of an exercise.
  2. will Java appear as a new job on the Travis build page (e.g., this one)? will raylet and non-raylet be in one job or two?

@jovany-wang
Copy link
Collaborator Author

jovany-wang commented Aug 6, 2018

@raulchen

  1. test_cluster.sh is an integration test. Execrise02 is just an App Demo, like Hello-World Sample. Execrise02 is used for test_cluster.sh.

  2. Of cause Java tests appear as job # 5. All java tests are in job # 5, and it means that whether raylet or non raylet is in job# 5.
    This is the job # 5 script:

 "script": [
    "./java/test.sh",
    "pushd java",
    "./test_cluster.sh",
    "popd"
  ],

import org.ray.core.RayRuntime;

/**
* HelloWorld example for tests, like test cluster.

Choose a reason for hiding this comment

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

test cluster -> test_cluster.sh

[[ ${start_process_log} =~ "Started Ray head node" ]] || exit 1
echo "Check[$1]: Ray all processes started."

execution_log=$(cat "./local_deploy/ray/run/org.ray.api.example.HelloExample/0.out.txt")

Choose a reason for hiding this comment

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

my PR changed the logging path to /tmp/raylogs, you should rebase and change this accordingly.

@jovany-wang
Copy link
Collaborator Author

Considering that we are going to get rid of RayCli, it's unnecessary to merge this PR.

@jovany-wang jovany-wang deleted the test_cluster_ci branch October 19, 2018 07:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants