Build completed at incorrect time in the timeline

[gkruse@…]

Just updated to 0.6b2 and the build now show an incorrect complete time in the timeline. I have a revision that was checked in at 12:26 pm pst and the build is shown completing at 4:31 am on the same day. This build took about 5 minutes to run. I suspect this is a problem with the timezone support. Please let me know if you require further information

[osimons]

Replying to gkruse@…:

Just updated to 0.6b2 and the build now show an incorrect complete time in the timeline.

Upgraded from what version? Any other information about server and slave timezone configuration that can help make sense of this? If you have SQL access to the project database, I'd really like to see the timestamps stored on the build - could you perhaps run this (replacing 91 with the ID of your build):

select rev_time, started, stopped from bitten_build where id=91;

[hodgestar]

Is it possible that the time on the slave was out of sync with the time on the master (or set to a different timezone)? If this was the case then this should be fixed by the resolution of #572. If would be useful if you could test this by trying out Bitten trunk or by locally applying the patch attached to #572.

[anatoly techtonik <techtonik@…>]

This can be closed after fix to #572 is released. I doubt that "trying out Bitten trunk" is doable for casual Bitten users. Lowering the priority as it is just a matter of simple check when 0.6rc1 is released.

[osimons]

Actually, we can just close it now as the code is committed to repos (trunk + 0.6 branch).