Fix multiple threads share one logger #720
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Wow, thanks @maoyixie! |
|
Unfortunately this seems to have the same problem: Does it work on your local machine? |
|
Sorry for the mistake. I have refixed and tested it on the local machine. |
|
Thanks for fixing this! |
|
/gcbrun exp -n my -ag |
|
Report looking good: Log shows different trial numbers too: |
DonggeLiu
approved these changes
Nov 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The original code (_fuzzing_pipelines, _fuzzing_pipeline, get_trial_logger) will cause multiple threads in the thread pool to share a logger. Now use threading.local() to create a separate logger for each thread.