Intland's free requirements, development and test management hosting.
This server hosts 110,000+ users on the cloud!
Showing time elapsed since a change in Synchronization View is inaccurate when committing#11707/v10
more
Tags:  not added yet

Showing time elapsed since a change in Synchronization View is inaccurate when committing[BUG-11707]

Tracker: Bugs Priority: NormalNormal Status: Closed
Submitted by: aron.gombas Apr 15, 2010 11:01 Modified by: ilya_ivanov Dec 08, 2010 08:54 Assigned to: ilya_ivanov Nov 24, 2010 04:42
Category: -- Severity: -- Resolution: Fixed
Release: -- Detected: --
Relations
Loading...
Description
Try this:
  1. make a change and commit it in Synchronization View, it says "5 seconds ago". so far so good
  2. work and an hour later commit an another change. the previous change is still "5 seconds ago" (not updated), and the second change is, say, "4 seconds ago"

Not critical, but misleading.

Details
Comments & Attachments (4)
Associations (0)
Children (0)
References (0)
SCM Commits (0)
All (0)

Filter
Submitted Comment
zkoppany
Nov 24, 2010 06:18
Your change is really simple and fixes the issue. No junit test is necessary.
ilya_ivanov
Nov 24, 2010 06:11
The problem was with date parsing pattern. But I will create a unit test for calculation anyway
zkoppany
Nov 24, 2010 04:42
With 1.7 the calculated time seems to be wrong for commits made after 12:00 am.
ilya_ivanov
Sep 23, 2010 08:13
Fixed. Now age is calculated based on change set creation date, without interaction with hg. But creation date doesn't save seconds, so newly created change sets will appear with label less than a minute ago