Closed Bug 1061987 Opened 10 years ago Closed 10 years ago

DXR is not updated as often as MXR

Categories

(Webtools Graveyard :: DXR, defect)

Product:
Webtools Graveyard
Component:
DXR
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: botond, Unassigned)

Details

(Whiteboard: mxr-parity) 

STR (on 2014-09-02):
  Search DXR for "RecordFrameMetrics" in mozilla-central.

Expected results:
  There are no results, because this function was renamed in a
  changeset that was merged to mozilla-central earlier today [1].

Actual results:
  There are results, suggesting that DXR is looking at an old
  version of the tree.

Note that an MXR search at the same time turns up no results, as expected.

[1] https://hg.mozilla.org/mozilla-central/rev/ea4cfd84e417
mozilla-central is rebuilt every 6 hours on DXR, as opposed to every 4 hours on MXR, so yes it is not updated as often. This is because m-c is actually compiled by DXR, while MXR simply does text indexing. This is not likely to change in the near future.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
There's also the issue that dxr doesn't update if c-c is broken, as was the case yesterday [1]. Any plans to change that?

[1] http://logs.glob.uno/?c=mozilla%23developers&s=29+Sep+2014&e=29+Sep+2014&h=kats#c1069760
Yep! https://wiki.mozilla.org/DXR_Parallel_Tree_Indexing

We'll probably hit that soon after the ES branch lands and request-time file rendering is done.
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.