-
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
rationalize use of suite stdout, stderr, and the log #386
Comments
Also, no need to preface an exception message with "ERROR", except at the outermost level. |
We agree with this proposal. |
We should also review what should go into the log in normal mode. There are lots of items which are probably not too useful and/or just repeating what would go into the suite runtime database file. |
We didn't really come to a consensus on exactly what should be in each of these files. We did agree that, at the least, we should review and document exactly what goes where. (including other files should as the job activity log). |
Since #2437, a running suite should no longer write to the |
Currently this is not very well organized. You really have to look at all three files to see what's going on if an error occurs.
Perhaps we should only use the log: it automatically time-stamps entries, it handles multiple threads nicely, and the amount of logging done is configurable.
The text was updated successfully, but these errors were encountered: