Skip to content

Conversation

@Lunderberg
Copy link
Contributor

Prior to this commit, the image_exists utility in determine_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 from tlcpackstaging, such as the current images tagged with 20240428-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 and logging.exception to instead use logging.debug.

Prior to this commit, the `image_exists` utility in
`determine_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 from `tlcpackstaging`,
such as the current images tagged with `20240428-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` and
`logging.exception` to instead use `logging.debug`.
@Lunderberg Lunderberg merged commit 538343f into apache:main Jul 31, 2024
@Lunderberg Lunderberg deleted the ci_lower_loglevel_for_docker_tlcpackstaging branch July 31, 2024 15:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants