[ENH] testing `ray` parallelization but avoiding long test runtimes and hangs

[fkiraly]

Currently, we have adopted the sktime parallelization backend dispatcher, inheriting the issues with ray and testing ray, e.g., long runtimes, sporadic crashes in the CI - parallel issue in sktime here: sktime/sktime#8149

We should monitor sktime #8149 and apply the same fix to hyperactive (or scikit-base after a potential refactor). For now, we have decided to skip the ray related testing.

[pankajbaid567]

Thanks for the context! 👋

I reviewed sktime/sktime#8149 and the related discussion around Ray reliability in CI. Skipping Ray-dependent tests for now makes sense given the instability and runtime concerns.

I’ll keep an eye on the progress upstream, and once a stable fix or pattern emerges, I can help apply the same approach here (either in the current Hyperactive setup or after the scikit-base refactor, depending on timing).

In the meantime, if there's any smaller isolated task—like marking tests with expected failures, adding better CI guards, or improving documentation around Ray usage—I’m happy to pick that up.