mirror of
https://github.com/wassname/ray.git
synced 2026-07-24 13:20:22 +08:00
Robert NishiharaandRichard Liaw
75504b9586
Running `./ci/long_running_tests/start_workloads.sh` will start several workloads running (each in their own EC2 instance). - The workloads run forever. - The workloads all simulate multiple nodes but use a single machine. - You can get the tail of each workload by running `./ci/long_running_tests/check_workloads.sh`. - You have to manually shut down the instances. As discussed with @ericl @richardliaw, the idea here is to optimize for the debuggability of the tests. If one of them fails, you can ssh to the relevant instance and see all of the logs.
25 lines
655 B
Bash
Executable File
25 lines
655 B
Bash
Executable File
#!/usr/bin/env bash
|
|
|
|
# set -x
|
|
|
|
ROOT_DIR=$(cd "$(dirname "${BASH_SOURCE:-$0}")"; pwd)
|
|
|
|
pushd "$ROOT_DIR"
|
|
|
|
for workload_file in "$ROOT_DIR"/workloads/*; do
|
|
file_name=$(basename -- $workload_file)
|
|
workload_name="${file_name%.*}"
|
|
echo "======================================================================"
|
|
echo "WORKLOAD: $workload_name"
|
|
echo "======================================================================"
|
|
|
|
ray exec config.yaml --cluster-name="$workload_name" "tmux capture-pane -p"
|
|
echo ""
|
|
echo "ssh to this machine with:"
|
|
echo " ray attach $ROOT_DIR/config.yaml --cluster-name=$workload_name"
|
|
echo ""
|
|
echo ""
|
|
done
|
|
|
|
popd
|