remove unnecessary log messages #11065
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
sebasgomez238
approved these changes
Dec 5, 2024
1c847f0 to
da69715
Compare
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.
Clean up log messages added in #11055.
Originally the log messages were to debug why a file generated during
fetch_fileswasn't present for the subsequent call toupdate_files. I've since learned that in certain instances, update jobs can run those two commands in separate containers with no shared filesystem.The fix to re-run discovery if needed is still the correct choice, so this only backs off the logging.
Recent telemetry shows that re-running the discovery has fixed the original issue.