This repository has been archived by the owner on Mar 3, 2023. It is now read-only.
Clean up executor logging in LocalScheduler #1288
Merged
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.
Executor log files in LocalScheduler currently look like this:
Two issues:
This changes executor logging to look more like the logging of the other processes. If you have two executors you'd see something like this:
If one fails and is restarted, it continues to log to the same file as the previous instance.