Update log level in scheduler critical section edge case #30694
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
This log message can be useful if the scheduler ends up needing to query TIs more than once per scheduler loop, so make it INFO vs DEBUG to increase discoverability.
boring-cyborg
bot
added
the
area:Scheduler
uranusjr
approved these changes
Apr 18, 2023
potiuk
approved these changes
Apr 22, 2023
|
Maybe 2.6.0 @jedcunningham @ephraimbuddy @pierrejeambrun ? |
|
I don't see any harm in it, but it also isn't really needed either. |
|
ok. Remove then. |
ephraimbuddy
pushed a commit
that referenced
this pull request
Apr 23, 2023
This log message can be useful if the scheduler ends up needing to query TIs more than once per scheduler loop, so make it INFO vs DEBUG to increase discoverability. (cherry picked from commit 3f5280b)
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.
This log message can be useful if the scheduler ends up needing to query TIs more than once per scheduler loop, so make it INFO vs DEBUG to increase discoverability.