Closed
Bug 884295
Opened 12 years ago
Closed 10 years ago
Hg pushlog does not load via hg.mozilla.org
Categories
(Developer Services :: Mercurial: hg.mozilla.org, defect)
Developer Services
Mercurial: hg.mozilla.org
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: whimboo, Unassigned)
References
()
Details
(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/746] )
When you try to load the following page, the loading of the page gets stalled:
http://hg.mozilla.org/releases/mozilla-release/pushloghtml
Loading the following URL works:
http://hg.mozilla.org/releases/mozilla-release/
Comment 1•12 years ago
|
||
hgweb is running into the 5 minute timeout, which is why nothing's appearing. /pushlog/ works, too. We'll see if we can sort something out.
| Reporter | ||
Comment 2•12 years ago
|
||
Do we have an update here? It's annoying that the pushlog does not work.
Severity: normal → major
Comment 3•12 years ago
|
||
There is no fix. If we can make pushlog more efficient, that would be the way to go. IT does not maintain pushlog, I've CC'ed Ted.
Severity: major → normal
Updated•12 years ago
|
Assignee: server-ops-devservices → nobody
Component: Server Operations: Developer Services → Hg: Customizations
QA Contact: shyam
Comment 4•12 years ago
|
||
the issue here is that it was a single push to -release from the uplift where pushlog fetches from hg details on every change... which is every change for the last 18 weeks since this release was on trunk.
Comment 5•12 years ago
|
||
For the sake of clarification, we often hit this issue on mozilla-release, mozilla-beta, and mozilla-aurora after a merge from their parent repo. There are several older bugs like this one.
As fox2mike and fubar say, the underlying issue is the performance of pushlog+hg, for the case of having a large number of changesets in a single push. It tends to go away as more pushes land in the repo the big merge 'scrolls off' the bottom of the first page of pushloghtml. That happens fastest on aurora and beta, but can persist on mozilla-release because it's very low traffic.
Comment 6•12 years ago
|
||
I don't know what the right fix is here. We could sacrifice correctness in the data when loading the default HTML page and not load the entire contents of huge pushes, just display (nnnnnn changesets).
| Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
| Assignee | ||
Updated•11 years ago
|
Product: Release Engineering → Developer Services
Updated•11 years ago
|
Whiteboard: [kanban:engops:https://kanbanize.com/ctrl_board/6/82]
Updated•11 years ago
|
Whiteboard: [kanban:engops:https://kanbanize.com/ctrl_board/6/82] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/746] [kanban:engops:https://kanbanize.com/ctrl_board/6/82]
| Assignee | ||
Updated•11 years ago
|
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/746] [kanban:engops:https://kanbanize.com/ctrl_board/6/82] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/746]
Comment 8•10 years ago
|
||
GPS, I am not sure why you nied me. I never saw that issue.
Flags: needinfo?(sledru) → needinfo?(gps)
Comment 9•10 years ago
|
||
I figured you being a release manager would know about this.
Flags: needinfo?(gps)
| Reporter | ||
Comment 10•10 years ago
|
||
As the reporter of this bug I checked the both links which I have given at that time and I can no longer see this hang. So I would assume nothing needs to be done here anymore.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•