google-code-backups / xinc

Automatically exported from code.google.com/p/xinc
0 stars 0 forks source link

Cron schedule incorrected #157

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Cron is set to "* */3 * * *" - every 3 hours.
On start xinc, project was built. Last log entries:

[info]   [2008-04-09 11:52:32-Europe/Kiev] [build] Telme: Processing
publishers done
 [info]   [2008-04-09 11:52:32-Europe/Kiev] Setting loglevel to 2
 [info]   [2008-04-09 11:52:32-Europe/Helsinki] Next buildtime: 2008-04-09
12:00:00
 [info]   [2008-04-09 11:52:32-Europe/Helsinki] Sleeping: 448 seconds

Question #1: Why next time is 2008-04-09 12:00:00? (May be, it is because
there are two projects in xinc?)
Question #2: Now it is 12:00:07, but now build currently running

Original issue reported on code.google.com by kingo...@gmail.com on 9 Apr 2008 at 9:09

GoogleCodeExporter commented 8 years ago
To clarify the problem, lets see:
oleg@shoom-alpha:~$ tail /var/log/xinc.log
 [info]   [2008-04-09 23:40:54-Europe/Kiev] Setting loglevel to 2
 [info]   [2008-04-09 23:40:54-Europe/Helsinki] Next buildtime: 2008-04-10 09:00:00
 [info]   [2008-04-09 23:40:54-Europe/Helsinki] Sleeping: 33546 seconds
oleg@shoom-alpha:~$ php
<?php
echo date('Y-m-d H:i:s', strtotime('2008-04-10 09:00:00')+33546);
echo PHP_EOL;

2008-04-10 18:19:06
oleg@shoom-alpha:~$ 

Original comment by kingo...@gmail.com on 10 Apr 2008 at 7:38

GoogleCodeExporter commented 8 years ago
I am wrong in my last comment.
oleg@shoom-alpha:$ php
<?php
echo date('Y-m-d H:i:s', strtotime('2008-04-09 23:40:54')+33546);
echo PHP_EOL;

2008-04-10 09:00:00
oleg@shoom-alpha:$ php

It calculates time correct, but seems like cycle of a log usleep can get more 
time,
that we want.

Original comment by kingo...@gmail.com on 10 Apr 2008 at 8:10

GoogleCodeExporter commented 8 years ago
Hi Oleg,

thanks. I am on the issue, I have experienced it myself. Stay tuned ;)

Arno

Original comment by arnos...@gmail.com on 10 Apr 2008 at 8:43

GoogleCodeExporter commented 8 years ago

Original comment by arnos...@gmail.com on 11 Apr 2008 at 7:32

GoogleCodeExporter commented 8 years ago
The above mentioned case was tested and should be fixed in the latest trunk 
version
build.181

Please verify

Original comment by arnos...@gmail.com on 1 May 2008 at 9:29

GoogleCodeExporter commented 8 years ago
worked on a usleep problem, timer runs now as setup

Original comment by arnos...@gmail.com on 8 May 2008 at 6:20