-
Notifications
You must be signed in to change notification settings - Fork 94
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
Cleaned up logging a little #3836
Cleaned up logging a little #3836
Conversation
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.
Seems reasonable, thanks @wxtim 👍
Yep, we should keep the subprocpool logging, it is very helpful. Can remove (3) as well since it doesn't give us any information that (2) doesn't, note (2) will also give us stderr if it occurs which is very helpful. |
Are you suggesting restoring (2) and removing (3) @oliver-sanders ? (@wxtim did the opposite of that). |
Happy to do whatever, but would prefer agreement first... |
Aah, I thought (2) had come from the subprocpool, but it was (1). |
* master: (36 commits) Cleaned up logging a little (cylc#3836) Platform from platform group basic unit test (cylc#3832) added reqd test_header tid platform tests scan: improve colour output spelling error fix scan: fix hier suites test: old host/batch system configs don't conflict with dummy-local mode Fix task message validation for multiline messages Fix spelling error. removed cylc7 data structure removed unused endpoints Commands migrated to GraphQL endpoint cli: rename spawn -> set-outputs Update changelog Remove test_unicode_rules Do not allow any colons in task outputs Fix command help. Correct typo. Upgraded new test. ...
Follow up to #3791 focused on comments from @oliver-sanders reproduced here:
The log messages contain a bit of duplicated info and could do with being tidied up a bit:
One message should suffice for this case, note the second log message comes from the subprocpool and contains all the required info.
One message should suffice for this case, the traceback isn't helpful here as we already know where the exception was raised from.
Treating each message in order:
subprocpool.py
: I'm a bit reluctant to remove this, since I haven't changed it, and I fear that other things may require it.