You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FIX-#7684: When we exceed max_cost for all available Backends an error may occur (#7685)
The BackendCostCalculator was originally designed to return None when no
suitable backend was available. It would do this when the max_cost of
all backend were exceeded. In practice, and with changes related to
considering multiple backends for pre-operation switches it was realized
that this was too restrictive and it would throw a ValueError under
certain workloads.
This change allows the calculator to first calculate a backend
considering max_cost but, if one is not found, then calculate one
disregarding max_cost. A backend should always be returned in this case.
## What do these changes do?
- [x] first commit message and PR title follow format outlined
[here](https://modin.readthedocs.io/en/latest/development/contributing.html#commit-message-formatting)
> **_NOTE:_** If you edit the PR title to match this format, you need to
add another commit (even if it's empty) or amend your last commit for
the CI job that checks the PR title to pick up the new PR title.
- [x] passes `flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py`
- [x] passes `black --check modin/ asv_bench/benchmarks
scripts/doc_checker.py`
- [x] signed commit with `git commit -s` <!-- you can amend your commit
with a signature via `git commit -amend -s` -->
- [x] Resolves#7684
- [x] tests added and passing
- [x] module layout described at `docs/development/architecture.rst` is
up-to-date <!-- if you have added, renamed or removed files or
directories please update the documentation accordingly -->
0 commit comments