What kind of indexing breakage are you talking about?  Surely we can detect
it in the indexer script, and choose not to flip a broken index with a
pre-existing good one?

--
Ehsan
<http://ehsanakhgari.org/>


On Tue, Feb 7, 2012 at 10:03 AM, Lionel Dricot <[email protected]> wrote:

> Hello,
>
> A big problem of DXR currently is that it takes a very long time to
> index a big project like mozilla-central and, during the whole time, DXR
> appears broken.
>
> Taras idea was to make the indexing process atomic: save everything in
> one place then mv once it is finished.
>
> But I realize that, sometimes, the indexing fails and, if you don't
> realize it immediately, DXR still looks broken for users. My idea is
> then to test what we have indexed and only copy that to the final
> location if it looks fine. (sending an email to the user requesting the
> indexing if it fails)
>
> My question now is: do you have any idea on how we could make a generic
> test that ensure that the indexing went mostly good?
>
> Any idea is welcome,
>
> Lionel
> _______________________________________________
> dev-static-analysis mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/dev-static-analysis
>
_______________________________________________
dev-static-analysis mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-static-analysis

Reply via email to