-
Notifications
You must be signed in to change notification settings - Fork 388
[Feature] Add CI for fault tolerance #1222
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| def simulate_crash(self): | ||
| logger.warning(f"Simulating crash on engine {self.server_host}:{self.server_port}...") | ||
| kill_process_tree(self.process.pid) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Guard simulate_crash when no local process exists
The new simulate_crash unconditionally dereferences self.process.pid, but self.process is only created in _init_normal; in --rollout-external mode (or any path where no local server process is launched), this attribute is never set. If CI enables fault injection in an external-engine setup, the Ray task will raise AttributeError instead of simulating a crash, which defeats the test and can break the rollout manager. Consider checking self.args.rollout_external (or self.process is not None) before calling kill_process_tree.
Useful? React with 👍 / 👎.
No description provided.