Log client addresses in scheduler lifecycle messages#9270
Conversation
Signed-off-by: peter941221 <peter941221@gmail.com>
Signed-off-by: peter941221 <peter941221@gmail.com>
Unit Test ResultsSee test report for an extended history of previous test failures. This is useful for diagnosing flaky tests. 40 files + 9 40 suites +9 14h 10m 21s ⏱️ + 3h 22m 3s For more details on these failures, see this check. Results for commit 7e97188. ± Comparison against base commit d8fabe2. This pull request removes 22 and adds 102 tests. Note that renamed tests count towards both.This pull request removes 13 skipped tests and adds 88 skipped tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
|
Current red jobs look unrelated to this patch. This PR only changes |
Summary
ClientStateso the same address is available throughout the client lifecycleCloses #8000
Testing
python -m py_compile distributed/scheduler.py distributed/tests/test_scheduler.pypython -m pytest distributed/tests/test_scheduler.py -k client_connection_logs_include_address(local environment is missingdask, so pytest fails during config import)