[lldb-dev] Pre-merge lldb testing

[Greg Clayton via lldb-dev]

> On May 15, 2020, at 7:04 PM, Eric Christopher via lldb-dev <lldb-dev at lists.llvm.org> wrote:
> 
> Hi All,
> 
> We've been testing[1] a number of patches upstream by default via some pre-merge checks in phabricator. I was thinking of turning them on for lldb as well. Mostly it well just help people know whether or not they've broken lldb before they commit something, but won't stop committing or do anything else that direction.

I am all for it! 

> Let me know what you think and otherwise I'd like to turn it on in a week or so. This will also help keep the test suite a little cleaner on linux FWIW.

Please do.

> There are a few additional links down below and if you have any questions send them my way.

Will the lldb tests be run automagically if and only if lldb code is modified in the patch? 

> 
> Thanks!
> 
> -eric
> 
> 
> [1] https://github.com/google/llvm-premerge-checks/blob/master/docs/user_doc.md <https://github.com/google/llvm-premerge-checks/blob/master/docs/user_doc.md>
> [2] https://reviews.llvm.org/project/members/78/ <https://reviews.llvm.org/project/members/78/> 
> [3] https://github.com/google/llvm-premerge-checks/issues <https://github.com/google/llvm-premerge-checks/issues>
> _______________________________________________
> lldb-dev mailing list
> lldb-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20200516/9ff0ef0e/attachment.html>