On 2/7/2012 1:53 PM, Lionel Dricot wrote:
Le 07/02/12 21:11, Taras Glek a écrit :
On 2/7/2012 7:03 AM, 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)
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?
In our project plan json queries are next on the list. I would solve
it by automatically running a few sample queries (ie a smoketest)
after a reindex. The sample queries on the homepage are good
candidates to testcasify.
That was my initial idea. But it is Mozilla-central specific, isn't it?
Yes. We can make a more general testsuite later.
Taras
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
