[PATCH] lit: Incremental test scheduling

[Sean Silva]

On Sun, Oct 27, 2013 at 10:09 PM, Alp Toker <alp at nuanti.com> wrote:

>
> On 28/10/2013 01:45, 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
> > <mailto: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.
>
> I agree, no build / test tool should touch the source directory so this
> feature isn't really ready for landing yet.
>
> I'm willing to take a stab at storing the cache in a local file, but
> wanted to gage the level of interest first.
>

FYI Python ships with sqlite in the stdlib: <
http://docs.python.org/3/library/sqlite3.html>. Depending on what exactly
you want to store and how you need to access it, it might be useful.

-- Sean Silva


>
> In my experience this is the kind of feature where once you have it,
> it's hard to go back :-)
>
> Alp.
>
>
> --
> http://www.nuanti.com
> the browser experts
>
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20131031/625309b0/attachment.html>