Closed Bug 458479 Opened 17 years ago Closed 17 years ago

MXR isn't working (reporting no result for strings that exist)

Categories

(mozilla.org Graveyard :: Server Operations, task)

task
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Gavin, Assigned: reed)

Details

Assignee: nobody → server-ops
Component: MXR → Server Operations
Product: Webtools → mozilla.org
QA Contact: mxr → mrz
Version: Trunk → other
metoo, but in a different root and multiple files. The strings in http://mxr.mozilla.org/comm-central/source/mail/locales/en-US/chrome/messenger-newsblog/newsblog.properties since they're used, appear both there and in at least one .js file, but searches like http://mxr.mozilla.org/comm-central/search?string=newsblog-invalidFeed return zero results.
mobile-browser is pretty broken too.
Summary: MXR not finding strings inside rules.mk on mxr.mozilla.org → MXR isn't working (reporting no result for strings that exist)
Assignee: server-ops → reed
Severity: normal → major
Ok, the 4-hour mxr cron was running over itself, so I rebooted the box to clear everything up, but the box didn't come back due to an issue with the network devices. That's been worked around for now, so box is back up. The box should start xreffing the 4-hour stuff again in about 50 minutes, so when that happens, the broken mxr trees should correct themselves. I'll check on this tomorrow morning to see if everything is better. I will also look into possibly moving some of the 4-hour cron trees to once-a-day to help ease up on that particular cron list.
Status: NEW → ASSIGNED
Looks like Gavin's search now works, but mine still fails.
Yeah, so the main issue is fixed, but there's still another problem. I'll open a bug under MXR for it, as it's something timeless will have to fix.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
(In reply to comment #4) > Looks like Gavin's search now works, but mine still fails. Comment #1 works for me?
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.