[ci][byod/2] move 9 more tests to byod

[can-anyscale]

Why are these changes needed?

Move 9 more release tests to byod

For context on why byod is preferrable: https://docs.google.com/document/d/12WU4vpR0jHgOwceoSgPtE4B-B-6mBonnHHiCSMmMNoY/edit

Checks

• I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
• I've run scripts/format.sh to lint the changes in this PR.
• Testing Strategy
  • Unit tests
  • Release tests - https://buildkite.com/ray-project/release-tests-pr/builds/40886

[ollie-iterators]

Speaking of the release tests, I've always been wondering, why do the release tests not run as much as the other tests? Does that mean that they never get removed from flakey-tests.ray.io?

[aslonnie]

why do the release tests not run as much as the other tests?

because they are relatively expensive to run.

Does that mean that they never get removed from flakey-tests.ray.io?

not sure what do you mean..

[ollie-iterators]

why do the release tests not run as much as the other tests?

because they are relatively expensive to run.

Does that mean that they never get removed from flakey-tests.ray.io?

not sure what do you mean..

The tests shown in the image below on https://flakey-tests.ray.io/ with "Show Release Tests" set to Only and "Show All" set to true have no failures and are still shown as flakey tests.

[aslonnie]

have no failures and are still shown as flakey tests.

that is probably a bug (or at least not desired behavior).. are you interested on fixing it?

The tracker is a static page generator that runs periodically, and the source code is here:
https://github.com/ray-project/travis-tracker-v2

Filed an issue here:
ray-project/travis-tracker-v2#39

Please follow up on that issue if you are interested.

Also, let's stop commenting about the flaky test tracker here, as it is not related to this PR.