Split python/ray/tests/test_actor_retry over two files
Why are these changes needed?
The test_actor_retry tests are failing/flaky on windows. They pass locally. I have not been able to access the CI logs to see what is going wrong. In order to shrink the problem (is it a overall timeout? Is one of the tests failing?) we can start by splitting the tests into two files.
Related issue number
Toward solving #43845.
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
- [ ] 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
- [ ] Release tests
- [ ] This PR is not tested :(
cc @anyscalesam
There are two overall strategies: TroubleMaker and AsyncTroubleMaker. I moved the (simpler) TroubleMaker-only tests to the new file, and left the ones that use the AsyncTroubleMaker
@anyscalesam @aslonnie any more questions?
asking @rynewang @jjyao for opinions.
I'm ok with this.
Auto-merge did not trigger. Do I need to rebase the PR?