I believe pre-merge testing would be very useful.
The thing which I would find very useful (let's call it a feature
request) is to be able to get some sort of an overview/dashboard of all
the runs on this infrastructure and their results. It doesn't have to be
super detailed -- the question which
On Sat, May 16, 2020 at 12:18 PM Greg Clayton wrote:
>
>
> On May 15, 2020, at 7:04 PM, Eric Christopher via lldb-dev <
> lldb-dev@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 tur
> On May 15, 2020, at 7:04 PM, Eric Christopher via lldb-dev
> 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
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