I committed some code to a contrib project about an hour ago. The commit turns up on drupalcode.org, but that site thinks the code was commited over 2 days ago, which is wrong from wrongtown :-) The project page on d.o now also lists the same commit as 'a day ago', which is not right either.

See https://drupal.org/node/727336/commits and http://drupalcode.org/project/userpoints_evaporate.git/commit/a87c9c9519...

Comments

killes@www.drop.org’s picture

killes@www.drop.org CreditAttribution: killes@www.drop.org commented

Are you sure that you didn't make your local commit two days earlier than you pushed it to d.o?

cafuego’s picture

cafuego CreditAttribution: cafuego commented

Yes, 100% sure. I created the commit and pushed it immediately. However, I did travel from Australia to Portland before committing and pushing. I am pretty sure I worked on a local copy on a new VM and locally applied a patch after I had adjusted my local timezone.

I'm close to certain I didn't change my local timezone from Melbourne to Portland in between the commit and the push either.

Component: drupalcode.org » Git
Mixologic’s picture

Mixologic
He/Him/His
Primary language English
Location Portland, OR
CreditAttribution: Mixologic at Drupal Association commented
Issue summary: View changes
Status: Active » Closed (cannot reproduce)

If there are no other examples of commits being off, time wise, Im going to say that this was probably a timezone issue on either the VM or somehow crossing the dateline. In any case it hasnt happened again.