Closed
Bug 1121911
Opened 9 years ago
Closed 9 years ago
Inconsistent "Last change" date displayed in Repositories list
Categories
(Developer Services :: Mercurial: hg.mozilla.org, defect)
Developer Services
Mercurial: hg.mozilla.org
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: flod, Unassigned)
Details
Attachments
(1 file)
370.93 KB,
image/png
|
Details |
Take for example this page https://hg.mozilla.org/releases/gaia-l10n/v2_0 Reload it multiple times, the "Last change" date will sometimes change for some repositories. See for example the attached file: it's the same URL, taken at 20 seconds from each other.
Comment 1•9 years ago
|
||
That looks like some webheads are not up-to-date.
Comment 2•9 years ago
|
||
Wow, and some of those go back quite a ways, before we made fixes to the web head syncing. :-( Will start doing manual syncs to get things up to date.
Assignee: nobody → klibby
Comment 3•9 years ago
|
||
Forced syncs, checked data and was still seeing mismatched dates. It turns out that the "Last Changed" column is based on the filesystem timestamp and not the time of the last commit. Based on the various time stamps, I expect this is due to the rebuilding of the hg web heads; they were done over the course of a month or two last summer. Thus, if v2_0/be was synced on a few nodes before the Jul 2015 push and the rest were synced after, the "Last changed" date appears differently. I'm not sure that we'd want to query each and every repo when viewing a directory like that - git.m.o does and it can be extremely slow. I'm going to unassign myself since I'm going on PTO tomorrow. Perhaps :gps has thoughts on this.
Assignee: klibby → nobody
Comment 4•9 years ago
|
||
It's not realistic to have indexes list the last commit or push date from each repo. That would involve too much CPU and I/O to render index pages.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•