-
-
Notifications
You must be signed in to change notification settings - Fork 712
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Log worker info on error #7947
Log worker info on error #7947
Conversation
Unit Test ResultsSee test report for an extended history of previous test failures. This is useful for diagnosing flaky tests. 20 files ±0 20 suites ±0 11h 23m 50s ⏱️ - 41m 13s For more details on these failures, see this check. Results for commit 23ce7b3. ± Comparison against base commit 4c4748a. ♻️ This comment has been updated with latest results. |
Instead of: 2023-06-23 15:37:47,237 - distributed.worker - WARNING - Compute Failed
Key: f-78eea523b6ed747be234c3bfbc24c116
Function: f
args: ()
kwargs: {}
Exception: 'BadNumbers(1, 2.5, 3)'
2023-06-23 15:37:47,238 - distributed.client - ERROR - in task: f-78eea523b6ed747be234c3bfbc24c116
on worker:{'tcp://127.0.0.1:54346'} Wouldn't it be much cleaner and simpler to just add a line to the already existing message? 2023-06-23 15:37:47,237 - distributed.worker - WARNING - Compute Failed
Key: f-78eea523b6ed747be234c3bfbc24c116
Function: f
args: ()
kwargs: {}
Exception: 'BadNumbers(1, 2.5, 3)'
Worker: tcp://127.0.0.1:54346 |
It's not so easy, unfortunately. I wish every Python exception had something like a read-write This PR is based on your suggestion here: |
…up-remote-tracebacks-2
…up-remote-tracebacks-2
@crusaderky I made changes as we discussed. The message emitted on client is now very similar to the one emitted on worker. |
ae00614
to
b71375d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.
Different version of #7847.
pre-commit run --all-files
How this works: