Skip to content

fix: too many logs on cronjob#1807

Open
MarceloRobert wants to merge 1 commit intokernelci:mainfrom
MarceloRobert:fix/cronjob-log
Open

fix: too many logs on cronjob#1807
MarceloRobert wants to merge 1 commit intokernelci:mainfrom
MarceloRobert:fix/cronjob-log

Conversation

@MarceloRobert
Copy link
Collaborator

Postgres start_time is already timezone-aware, meaning that we don't need to try to make it aware and log the error all the time

Closes #1806

Postgres start_time is already timezone-aware, meaning that we don't need to try to make it aware and log the error all the time
@MarceloRobert MarceloRobert self-assigned this Mar 17, 2026
@MarceloRobert MarceloRobert added bug Something isn't working Backend Most or all of the changes for this issue will be in the backend code. labels Mar 17, 2026
Comment on lines +81 to +84
if old_checkout_start_time > cached_start_time:
return True
else:
return False
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you could just return old_checkout_start_time > cached_start_time

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Backend Most or all of the changes for this issue will be in the backend code. bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Checkout cache cronjob has too many logs

2 participants