-
Notifications
You must be signed in to change notification settings - Fork 49
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
Intermixed info in log file when processing multiple files #564
Comments
If mbinc is processing mult mbin in parallel then messages written to single log will be mixed. The easiest way to prevent this is to have each mbin instance maintain its own log (list) of messages, then write them all to the log once the mbin finishes processing. The write to the log would be serialized, so although all messages for a given mbin would be together the order that the mbin's are reported would be random (depends when a thread finishes a given mbin). If you want mbin's in order as well then wait until all mbin's finish then write to log, however, then carrying state around for each mbin after it's finished which won't scale well ... though for this case would likely be ok. Other issue is if crash, then won't have messages in log upto crash point. |
Thanks for comment. |
From Discord:
|
MBINCompiler is called like this:
|
Describe the bug
Intermixed info in log file when processing multiple files
Expected behavior
Each processed file info in its block of text
Steps To Reproduce
Process a large amount of files that generate a mix of WARN and/or ERR as well as no WARN/ERR (just INFO lines)
Specs (please complete the following information, if applicable):
Attachments:
see example log output
MBINCompiler.log
![Screenshot - 2023-08-14 , 22_31_14](https
![Screenshot - 2023-08-14 , 22_30_57](https://gith
ub.com/monkeyman192/MBINCompiler/assets/3037251/c5a28a20-4c16-478d-8f21-e8b735a3b51a)
://github.com/monkeyman192/MBINCompiler/assets/3037251/103d1393-faf7-4210-b49b-d13c154f437e)
The text was updated successfully, but these errors were encountered: