Hey hey, On mar, 2012-02-07 at 16:03 +0100, Lionel Dricot 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)
I wonder if that should be handled at a higher level, dxr-index is just the final step of the operation, so we could be missing (or hiding) errors at other levels. > > 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? Far from generic, but I tend to think that some error propagation should happen between the several indexing plugins and the main dxr-index script, those know best how to ensure data consistency on their hand. The web side also seems to have hardcoded requisitions on data generated by some of those modules (eg, cxx-clang), so it could be worth adding a way to make plugins mandatory/optional and handle those as gracefully as possible. Carlos _______________________________________________ dev-static-analysis mailing list [email protected] https://lists.mozilla.org/listinfo/dev-static-analysis
