[CI] Reduce logging level when checking if docker image exists #17221
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.
Prior to this commit, the
image_exists
utility indetermine_docker_images.py
logged the full response for success, and the full HTTP error if an exception is caught. However, this is the expected behavior when loading a docker image fromtlcpackstaging
, such as the current images tagged with20240428-060115-0b09ed018
. Logging this fallback as an error makes it difficult to find the first actual error that occurred in CI.This commit updates these logging statments
logging.info
andlogging.exception
to instead uselogging.debug
.