dask / dask/distributed

Untested behaviour when decide_worker returns None

Open
#8,156 0 comments 0 reactions 0 assignees View on GitHub
tests
Dominant language
Python
Stars
1.7k
Forks
778
Avg merge
2h 50m
Merged PRs (30d)
3

Description

Accidentally, while I was developing https://github.com/dask/distributed/pull/8135 , coveralls highlighted that there are no tests for what happens when
`transition_no_worker_processing` or `transition_queued_processing` fail to transition the task to processing because `decide_worker_non_rootish` or `decide_worker_rootish_queuing_enabled` (respectively) returned None.

There may be other use cases.
It feels too big of a corner case, with too much potential for deadlocking, to leave it untested.

CC @fjetter @hendrikmakait

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.