-
Notifications
You must be signed in to change notification settings - Fork 6.6k
Open
Labels
P2Important issue, but not time-criticalImportant issue, but not time-criticalbugSomething that is supposed to be working; but isn'tSomething that is supposed to be working; but isn'tcoreIssues that should be addressed in Ray CoreIssues that should be addressed in Ray Corecore-apiusability
Description
What happened + What you expected to happen
When starting Ray with the command "ray start --head --block,", it will not exit if you attempt to terminate it using the "ray stop" command. However, if using the "ray stop -f" command to terminate it, the start command will return an exit code of 1.
In our environment, we would like the start command line to exit with an exit code of 0 when terminated with the "ray stop" command because this is not considered an exceptional situation.
Why does "ray start" always exit with an exit code of 1? Is it possible to exit with a code of 0 when receiving the expected return code?
Versions / Dependencies
ray 2.8.1
Reproduction script
ray start --head --block
ray stop/ray stop -f
Issue Severity
High: It blocks me from completing my task.
Metadata
Metadata
Assignees
Labels
P2Important issue, but not time-criticalImportant issue, but not time-criticalbugSomething that is supposed to be working; but isn'tSomething that is supposed to be working; but isn'tcoreIssues that should be addressed in Ray CoreIssues that should be addressed in Ray Corecore-apiusability