If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

comm-central MXR no longer updates

VERIFIED FIXED

Status

mozilla.org Graveyard
Server Operations
--
critical
VERIFIED FIXED
9 years ago
3 years ago

People

(Reporter: mcsmurf, Assigned: reed)

Tracking

Details

(URL)

(Reporter)

Description

9 years ago
The mxr repository under http://mxr.mozilla.org/comm-central/ no longer seems to update, it looks like the last update was on the 9th of September. For an example compare http://hg.mozilla.org/comm-central/annotate/713c34b1a232/mailnews/imap/src/nsImapIncomingServer.cpp#l2691 to http://mxr.mozilla.org/comm-central/source/mailnews/imap/src/nsImapIncomingServer.cpp#2694.
This bug here might have to do with Bug 453973, the issue has also been mentioned there a few days ago, but nothing seems to happen.
(Assignee)

Updated

9 years ago
Assignee: server-ops → reed
As we're heading towards 3.0b1, getting accurate mxr is pretty critical, so raising severity level.
Severity: major → critical
(Assignee)

Comment 2

9 years ago
I can clear it up, but it just messes up again after a while... I don't know if this a client.py problem, Hg problem, or mxr problem. :/
(Assignee)

Comment 3

9 years ago
It's back, but no doubt it'll screw up again.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Probably a mercurial bug, tracked upstream here: http://www.selenic.com/mercurial/bts/issue1313

Comment 5

7 years ago
http://hg.intevation.org/mercurial/crew/rev/9f0e52e1df77 is supposed to have fixed that issue
Status: RESOLVED → VERIFIED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.