Ticket #3097 (closed defect: invalid)
Opened 6 years ago
Last modified 5 years ago
wrong time in revision log
| Reported by: | anonymous | Owned by: | jonas |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | timeline | Version: | 0.10.3 |
| Severity: | normal | Keywords: | |
| Cc: | |||
| Release Notes: | |||
| API 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
Change History
comment:1 Changed 6 years ago by anonymous
- Resolution set to invalid
- Status changed from new to closed
comment:2 follow-up: ↓ 3 Changed 5 years ago by philip@…
- Component changed from browser to timeline
- Resolution invalid deleted
- Status changed from closed to reopened
- Version changed from 0.9.5 to 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 in reply to: ↑ 2 Changed 5 years ago by cboos
Did you resync? Otherwise, it's normal you still have the times of before the hardware clock reset, as those times were cached.
comment:4 Changed 5 years ago by anonymous
Yes I did a resync, a workaround to this problem would feasible for me.
comment:5 Changed 5 years ago by philip@…
Forgot to set my email address in the previous comment
comment:6 Changed 5 years ago by anonymous
- Resolution set to invalid
- Status changed from reopened to 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
hwclock was set correctly, but date command shows wrong date and time. It's server-side problem, invalid ticket.