Run any task and check time that logging messages print. Worked on my machine.
Details
Details
Diff Detail
Diff Detail
- Repository
- rLTRN libtaskotron
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Comment Actions
Can you please also add a timezone specifier into the log format, now that we don't default to local time? I.e. instead of this
[libtaskotron:runner.py:231] 2015-02-17 08:07:08 DEBUG Using libtaskotron 0.3.11
it would be something like this
[libtaskotron:runner.py:231] 2015-02-17 08:07:08 UTC DEBUG Using libtaskotron 0.3.11
Thanks.
Comment Actions
So, I'm not all that enamoured with the GMT time and the timezone in the same log lines. With this patch, I get stuff like the following on my machine:
[libtaskotron:runner.py:255] 2015-02-17 11:46:16 +0000 INFO Check execution finished.
I'm of the mind that we either use UTC or put the timezone in there. Using both is silly
Comment Actions
After discussion with Tim, we think it should be sufficient to print the full timestamp including the timezone at the execution start (and possibly the end), and then drop the timezone from the generic logging header displayed on every line. So something like this:
[libtaskotron:runner.py:231] 2015-02-17 08:07:00 INFO Execution started at: 2015-02-17 08:07:00 +0000 [libtaskotron:runner.py:231] 2015-02-17 08:07:08 DEBUG Using libtaskotron 0.3.11 [libtaskotron:runner.py:231] 2015-02-17 08:07:10 DEBUG Look, I'm doing some stuff! [libtaskotron:runner.py:231] 2015-02-17 08:07:20 INFO Execution finished at: 2015-02-17 08:07:20 +0000