ray
ray copied to clipboard
ray-project
when actor_id_ is nil ,call ray.get_runtime_context().actor_name will cause raise
Why are these changes needed?
when actor_id_ is nil ,call ray.get_runtime_context().actor_name will cause raise
Related issue number
Checks
- [x] I've signed off every commit(by using the -s flag, i.e.,
git commit -s) in this PR. - [x] I've run
scripts/format.shto 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.rstfile.
- [ ] I've added any new APIs to the API Reference. For example, if I added a
method in Tune, I've added it in
- [x] 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
- [x] Release tests
- [ ] This PR is not tested :(
Would you mind rebasing with the master branch?
@kevin85421 not mind, how need i do
Take a look at your commit history. It seems to be that you don't sync with the master branch correctly. You may not need to rebase with the master branch, but you need to fix your commit history.
@kevin85421 It seems that some of the test cases timed out, causing the use cases to fail, how should I re-triggered the C test
It seems that some of the test cases timed out, causing the use cases to fail, how should I re-triggered the C test
I re-triggered CI pipeline multiple times for this PR. It always fails. Could you try to reproduce in your local env?
@kevin85421 These test cases have bugs, and someone merged and fixed them two days ago
@kevin85421 These test cases have bugs, and someone merged and fixed them two days ago
Would you mind rebasing with the master branch? Thanks!
@kevin85421 not mind, how need i do
@kevin85421 not mind, how need i do
Sync your branch with the upstream master branch.