From 65b41eb2910f2194a4a41cf8f71c51c5a51a5db7 Mon Sep 17 00:00:00 2001 From: Fabien Meghazi Date: Thu, 11 Jan 2018 17:00:21 +0100 Subject: [PATCH] [IMP] ir_cron: use 'info' loglevel instead of 'debug' when starting job This information is important for `ir.cron` troubleshooting hence deserves a little more love. --- odoo/addons/base/ir/ir_cron.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/odoo/addons/base/ir/ir_cron.py b/odoo/addons/base/ir/ir_cron.py index 375d9a966da..58dc0f06fb7 100644 --- a/odoo/addons/base/ir/ir_cron.py +++ b/odoo/addons/base/ir/ir_cron.py @@ -215,7 +215,7 @@ class ir_cron(models.Model): _logger.debug("Job `%s` already executed by another process/thread. skipping it", job['cron_name']) continue # Got the lock on the job row, run its code - _logger.debug('Starting job `%s`.', job['cron_name']) + _logger.info('Starting job `%s`.', job['cron_name']) job_cr = db.cursor() try: registry = odoo.registry(db_name)