Modify ↓
Opened 18 years ago
Closed 17 years ago
#3097 closed defect (invalid)
wrong time in revision log
| Reported by: | anonymous | Owned by: | Jonas Borgström |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | timeline | Version: | 0.10.3 |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
I don't know why but in revision logs Trac shows wrong "las update" time. svn list [URL] —verbose shows time correctly, so that is Trac problem
Attachments (0)
Change History (6)
comment:1 by , 18 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
follow-up: 3 comment:2 by , 17 years ago
| Component: | browser → timeline |
|---|---|
| Resolution: | invalid |
| Status: | closed → reopened |
| Version: | 0.9.5 → 0.10.3 |
After resetting the hardware clock(change timezone) we have the same problem
on win32 and trac 10.3 if i try the induvidual parts (python, svn, etc) they all show the right time except trac change log.
comment:3 by , 17 years ago
Did you resync? Otherwise, it's normal you still have the times of before the hardware clock reset, as those times were cached.
comment:6 by , 17 years ago
| Resolution: | → invalid |
|---|---|
| Status: | reopened → closed |
After resetting the machine, the time problem disappears, this is a windows issue. It seems that windows doesn't propagate the time change to the running processes, this still an issue e.g: ntp time updates for example.
Sorry
Note:
See TracTickets
for help on using tickets.
hwclock was set correctly, but
datecommand shows wrong date and time. It's server-side problem, invalid ticket.