Closed
Bug 1042403
Opened 10 years ago
Closed 10 years ago
DXR for comm-central busted, calling page returns 404/"Not found"
Categories
(Developer Services :: General, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: clokep, Assigned: fubar)
Details
c-c dxr [1] returns a 404 error and searching [2] gives a cryptic error:
> Something went wrong, good luck fixing it :)
>
> Failed to establish database connection.
[1] http://dxr.mozilla.org/comm-central/
[2] http://dxr.mozilla.org/comm-central/search?q=initializationPromise&redirect=true
Assignee | ||
Comment 1•10 years ago
|
||
Yep, known issue. How c-c builds changed recently and I need to reincorporate that into the dxr build process. More pressing issues have kept me from it, however.
Assignee: server-ops-devservices → klibby
Updated•10 years ago
|
Summary: DXR for c-c busted → DXR for comm-central busted, calling page returns 404/"Not found"
Assignee | ||
Comment 2•10 years ago
|
||
Making progress. Because of the broken building and word that c-c will likely have stability issues in building for the next few weeks, we've opted to go back to a known good build. Alas, *how* it's built has still changed apparently, so I'm having to inch my way through the process with help from callek, jcranmer and glandium.
Comment 3•10 years ago
|
||
Weird. How can the way it's built have changed for past, good-building changesets? Remember that we also have to pin an old moz-central, if you didn't already.
Assignee | ||
Comment 4•10 years ago
|
||
nfc, tbh, but the build script as-is still failed to build. and yes, both c-c and m-c are pinned to the revs jcranmer provided.
Honestly, if I can't get it to build this week, I'm probably going to back burner it and work on other trees. If I don't, I'll never get to them with hg and reviewboard work.
Comment 5•10 years ago
|
||
In the meantime, can we at least remove the [comm-central] section from the config file altogether so it doesn't show up in the menu and 404?
Comment 6•10 years ago
|
||
Also, thanks for all your work chasing this down, fubar. I agree with your prioritization plans.
Assignee | ||
Comment 7•10 years ago
|
||
(In reply to Erik Rose [:erik][:erikrose] from comment #5)
> In the meantime, can we at least remove the [comm-central] section from the
> config file altogether so it doesn't show up in the menu and 404?
oh, duh. of course! all set!
Assignee | ||
Comment 8•10 years ago
|
||
Attempting a new build of comm-central on staging, now that bug 1040009 is in.
Assignee | ||
Comment 9•10 years ago
|
||
Built successfully on staging using the versions in bug 1040009#c26. Will leave it pinned there for the moment since there was general bustage on the tree. And better than nothing at all.
Re-enabled on prod, so the next cron run will pick it up. In the mean time, it's available at http://dxr.allizom.org/ (and yes, the m-c tree there is 404ing until the next cron run).
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 10•10 years ago
|
||
Thanks for chasing this down. It will be great to have comm-central back!
Updated•10 years ago
|
Component: Server Operations: Developer Services → General
Product: mozilla.org → Developer Services
You need to log in
before you can comment on or make changes to this bug.
Description
•