[PATCH] lit: Incremental test scheduling

[Daniel Dunbar]

I like the functionality, but I will have to think some more about the
implementation.

I have already considered having lit maintain some sort of database of test
results. That would be useful for reporting things like flaky tests,
reporting performance test changes, and for this feature.

The other thing that would be really nice to open the door for would be if
lit could detect which tools have changed and only rerun tests for those
tools. Implementing this feature by having lit keep a database of test
results might provide a base for that...

I'll think some more about this and get back to you with some more concrete
ideas next week.

 - Daniel

On Sunday, October 27, 2013, Andrew Trick wrote:

> I really want this feature. It may not be clean, but would save a lot of
> time in practice. However...
>
> On Oct 24, 2013, at 10:35 PM, Alp Toker <alp at nuanti.com<javascript:_e({}, 'cvml', 'alp at nuanti.com');>>
> wrote:
>
> lit shell tests and compiled unit tests are both supported. At the moment,
> the cache is implemented by scanning and modifying test source mtimes
> directly. This hasn't caused trouble but the technique could be refined in
> future to store test failures in a separate cache file if needed.
>
>
> This doesn’t feel right. I don’t think it will personally cause me any
> grief, but seems like someone or their tools will be confused. If others
> think it’s ok, I won’t object. I just don’t want to accept the patch until
> others review this aspect.
>
> -Andy
>


-- 
- Daniel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20131027/b2196c6d/attachment.html>